mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-04-08 23:34:41 +03:00
Automatic translations update
This commit is contained in:
github-actions[bot]
committed by
GitHub
GitHub
parent
94a0a6c6ec
commit
c851bb5d32
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: matrix-docker-ansible-deploy \n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
|
||||
"POT-Creation-Date: 2026-03-31 05:49+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -573,254 +573,266 @@ msgid "How do I optimize this setup for a low-power server?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:308
|
||||
msgid "For a low-power server, it's best to use an alternative homeserver implementation (other than [Synapse](configuring-playbook-synapse.md))."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:310
|
||||
msgid "You can disable some not-so-important services to save on memory."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:327
|
||||
msgid "You can also consider implementing a restriction on room complexity, in order to prevent users from joining very heavy rooms:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:337
|
||||
#: ../../../docs/faq.md:317
|
||||
msgid "If you've installed [Jitsi](configuring-playbook-jitsi.md) (not installed by default), there are additional optimizations listed on its documentation page that you can perform."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:339
|
||||
#: ../../../docs/faq.md:320
|
||||
msgid "Synapse-specific optimizations"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:322
|
||||
msgid "If you're using [Synapse](configuring-playbook-synapse.md), you can also consider the following optimizations:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:332
|
||||
msgid "You can also consider [implementing a restriction on room complexity](configuring-playbook-synapse.md#limit-joining-heavy-rooms-on-constrained-hosts), in order to prevent users from joining very heavy rooms:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:340
|
||||
msgid "I already have Docker on my server. Can you stop installing Docker via the playbook?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:341
|
||||
#: ../../../docs/faq.md:342
|
||||
msgid "Yes, we can stop installing Docker ourselves. Just use this in your `vars.yml` file:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:347
|
||||
#: ../../../docs/faq.md:348
|
||||
msgid "I run another webserver on the same server where I wish to install Matrix. What now?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:349
|
||||
#: ../../../docs/faq.md:350
|
||||
msgid "By default, we install a webserver for you ([Traefik](https://doc.traefik.io/traefik/)), but you can also use [your own webserver](configuring-playbook-own-webserver.md)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:351
|
||||
#: ../../../docs/faq.md:352
|
||||
msgid "How is the effective configuration determined?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:353
|
||||
#: ../../../docs/faq.md:354
|
||||
msgid "Configuration variables are defined in multiple places in this playbook and are considered in this order:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:355
|
||||
#: ../../../docs/faq.md:356
|
||||
msgid "there are defaults coming from each role's defaults file (`role/matrix*/defaults/main.yml`). These variable values aim to be good defaults for when the role is used standalone (outside of this collection of roles, also called playbook)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:357
|
||||
#: ../../../docs/faq.md:358
|
||||
msgid "then, there are overrides in `group_vars/matrix_servers`, which aim to adjust these \"standalone role defaults\" to something which better fits the playbook in its entirety."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:359
|
||||
#: ../../../docs/faq.md:360
|
||||
msgid "finally, there's your `inventory/host_vars/matrix.example.com/vars.yml` file, which is the ultimate override"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:361
|
||||
#: ../../../docs/faq.md:362
|
||||
msgid "What configuration variables are available?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:363
|
||||
#: ../../../docs/faq.md:364
|
||||
msgid "You can discover the variables you can override in each role (`roles/*/*/defaults/main.yml`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:365
|
||||
#: ../../../docs/faq.md:366
|
||||
msgid "As described in [How is the effective configuration determined?](#how-is-the-effective-configuration-determined), these role-defaults may be overridden by values defined in `group_vars/matrix_servers`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:367
|
||||
#: ../../../docs/faq.md:368
|
||||
msgid "Refer to both of these for inspiration. Still, as mentioned in [Configuring the playbook](configuring-playbook.md), you're only ever supposed to edit your own `inventory/host_vars/matrix.example.com/vars.yml` file and nothing else inside the playbook (unless you're meaning to contribute new features)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:369
|
||||
#: ../../../docs/faq.md:381
|
||||
#: ../../../docs/faq.md:370
|
||||
#: ../../../docs/faq.md:382
|
||||
msgid "**Note**: some of the roles (`roles/galaxy/*`) live in separate repositories and are only installed after your run `just roles` (or `make roles`) or `just update` (which automatically does `git pull` and `just roles`)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:371
|
||||
#: ../../../docs/faq.md:372
|
||||
msgid "I'd like to adjust some configuration which doesn't have a corresponding variable. How do I do it?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:373
|
||||
#: ../../../docs/faq.md:374
|
||||
msgid "The playbook doesn't aim to expose all configuration settings for all services using variables. Doing so would amount to hundreds of variables that we have to create and maintain."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:375
|
||||
#: ../../../docs/faq.md:376
|
||||
msgid "Instead, we only try to make some important basics configurable using dedicated variables you can see in each role. See [What configuration variables are available?](#what-configuration-variables-are-available)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:377
|
||||
#: ../../../docs/faq.md:378
|
||||
msgid "Besides that, each role (component) aims to provide a `matrix_SOME_COMPONENT_configuration_extension_yaml` (or `matrix_SOME_COMPONENT_configuration_extension_json`) variable, which can be used to override the configuration."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:379
|
||||
#: ../../../docs/faq.md:380
|
||||
msgid "Check each role's `roles/*/*/defaults/main.yml` for the corresponding variable and an example for how use it."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:383
|
||||
#: ../../../docs/faq.md:384
|
||||
msgid "Installation"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:385
|
||||
#: ../../../docs/faq.md:386
|
||||
msgid "How do I run the installation?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:387
|
||||
#: ../../../docs/faq.md:388
|
||||
msgid "See [Installing](installing.md) to learn how to use Ansible to install Matrix services."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:389
|
||||
#: ../../../docs/faq.md:390
|
||||
msgid "However, we recommend you to follow our installation guide, instead of jumping straight to installing."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:391
|
||||
#: ../../../docs/faq.md:392
|
||||
msgid "There are two guides available:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:393
|
||||
#: ../../../docs/faq.md:394
|
||||
msgid "⚡ **[Quick start](quick-start.md)** (for beginners): this is recommended for those who do not have an existing Matrix server and want to start quickly with \"opinionated defaults\"."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:395
|
||||
#: ../../../docs/faq.md:396
|
||||
msgid "**Full installation guide (for advanced users)**: if you need to import an existing Matrix server's data into the new server or want to learn more while setting up the server, follow this guide by starting with the **[Prerequisites](prerequisites.md)** documentation page."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:397
|
||||
#: ../../../docs/faq.md:398
|
||||
msgid "I installed Synapse some other way. Can I migrate such a setup to the playbook?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:399
|
||||
#: ../../../docs/faq.md:400
|
||||
msgid "Yes, you can."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:401
|
||||
#: ../../../docs/faq.md:402
|
||||
msgid "You generally need to do a playbook installation. It's recommended to follow the full installation guide (starting at the [Prerequisites](prerequisites.md) page), not the [Quick start](quick-start.md) guide. The full installation guide will tell you when it's time to import your existing data into the newly-prepared server."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:403
|
||||
#: ../../../docs/faq.md:404
|
||||
msgid "This Ansible playbook guides you into installing a server for `example.com` (user IDs are like this: `@alice:example.com`), while the server is at `matrix.example.com`. If your existing setup has a server name (`server_name` configuration setting in Synapse's `homeserver.yaml` file) other than the base `example.com`, you may need to tweak some additional variables. This FAQ entry may be of use if you're dealing with a more complicated setup — [How do I install on matrix.example.com without involving the base domain?](#how-do-i-install-on-matrixexamplecom-without-involving-the-base-domain)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:405
|
||||
#: ../../../docs/faq.md:406
|
||||
msgid "After configuring the playbook and installing and **before starting** services (done with `ansible-playbook … --tags=start`) you'd import [your SQLite](importing-synapse-sqlite.md) (or [Postgres](importing-postgres.md)) database and also [import your media store](importing-synapse-media-store.md)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:407
|
||||
#: ../../../docs/faq.md:408
|
||||
msgid "I've downloaded Ansible and the playbook on the server. It can't connect using SSH."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:409
|
||||
#: ../../../docs/faq.md:410
|
||||
msgid "If you're using the playbook directly on the server, then Ansible doesn't need to connect using SSH."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:411
|
||||
#: ../../../docs/faq.md:412
|
||||
msgid "It can perform a local connection instead. Just set `ansible_connection=local` at the end of the server line in `inventory/hosts` and re-run the playbook."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:413
|
||||
#: ../../../docs/faq.md:414
|
||||
msgid "If you're running Ansible from within a container (one of the possibilities we list on our [dedicated Ansible documentation page](ansible.md)), then using `ansible_connection=local` is not possible."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:415
|
||||
#: ../../../docs/faq.md:416
|
||||
msgid "Maintenance and Troubleshooting"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:417
|
||||
#: ../../../docs/faq.md:418
|
||||
msgid "💡 Also see this page for generic information about maintaining the services and troubleshooting: [Maintenance and Troubleshooting](maintenance-and-troubleshooting.md)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:419
|
||||
#: ../../../docs/faq.md:420
|
||||
msgid "Do I need to do anything to keep my Matrix server updated?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:421
|
||||
#: ../../../docs/faq.md:422
|
||||
msgid "Yes. We don't update anything for you automatically."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:423
|
||||
#: ../../../docs/faq.md:424
|
||||
msgid "See our [documentation page about upgrading services](maintenance-upgrading-services.md)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:425
|
||||
#: ../../../docs/faq.md:426
|
||||
msgid "How do I move my existing installation to another (VM) server?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:427
|
||||
#: ../../../docs/faq.md:428
|
||||
msgid "If you have an existing installation done using this Ansible playbook, you can easily migrate that to another server following [our dedicated server migration guide](maintenance-migrating.md)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:429
|
||||
#: ../../../docs/faq.md:430
|
||||
msgid "If your previous installation is done in some other way (not using this Ansible playbook), see [I installed Synapse some other way. Can I migrate such a setup to the playbook?](#i-installed-synapse-some-other-way-can-i-migrate-such-a-setup-to-the-playbook)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:431
|
||||
#: ../../../docs/faq.md:432
|
||||
msgid "What is this `/matrix/postgres/data-auto-upgrade-backup` directory that is taking up so much space?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:433
|
||||
#: ../../../docs/faq.md:434
|
||||
msgid "When you [perform a major Postgres upgrade](maintenance-postgres.md#upgrading-postgresql), we save the the old data files in `/matrix/postgres/data-auto-upgrade-backup`, just so you could easily restore them should something have gone wrong."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:435
|
||||
#: ../../../docs/faq.md:436
|
||||
msgid "After verifying that everything still works after the Postgres upgrade, you can safely delete `/matrix/postgres/data-auto-upgrade-backup`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:437
|
||||
#: ../../../docs/faq.md:438
|
||||
msgid "I get \"Error response from daemon: configured logging driver does not support reading\" when I run `docker logs matrix-synapse`. Why?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:439
|
||||
#: ../../../docs/faq.md:440
|
||||
msgid "To prevent double-logging, Docker logging is disabled by explicitly passing `--log-driver=none` to all containers. Due to this, you cannot view logs using `docker logs matrix-*`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:441
|
||||
#: ../../../docs/faq.md:442
|
||||
msgid "See [this section](maintenance-and-troubleshooting.md#how-to-see-the-logs) on the page for maintenance and troubleshooting for more details to see the logs."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:443
|
||||
#: ../../../docs/faq.md:444
|
||||
msgid "The server fails to start due to the `Unable to start service matrix-coturn.service` error. Why and how to solve it?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:445
|
||||
#: ../../../docs/faq.md:446
|
||||
msgid "The error is most likely because Traefik cannot obtain SSL certificates due to certain reasons such as wrong domain name configuration or port 80 being unavailable due to other services."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:447
|
||||
#: ../../../docs/faq.md:448
|
||||
msgid "If Traefik fails to obtain an SSL certificate for domain names such as `matrix.`, Traefik Certs Dumper cannot extract the SSL certificate out of there, and coturn cannot be started and the error occurs. Refer to these comments for details:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:449
|
||||
#: ../../../docs/faq.md:450
|
||||
msgid "<https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3957#issuecomment-2599590441>"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:450
|
||||
#: ../../../docs/faq.md:451
|
||||
msgid "<https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4570#issuecomment-3364111466>"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:452
|
||||
#: ../../../docs/faq.md:453
|
||||
msgid "If you are not sure what the problem is, at first make sure that you have set the \"base domain\" (`example.com`, **not `matrix.example.com`**) to `matrix_domain`. You should be able to find it at the top of your `vars.yml`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:454
|
||||
#: ../../../docs/faq.md:455
|
||||
msgid "If it is correctly specified, look Traefik's logs (`journalctl -fu matrix-traefik.service`) for errors by Let's Encrypt for troubleshooting."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:456
|
||||
#: ../../../docs/faq.md:457
|
||||
msgid "Miscellaneous"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:458
|
||||
#: ../../../docs/faq.md:459
|
||||
msgid "I would like to see this favorite service of mine integrated and become available on my Matrix server. How can I request it?"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:460
|
||||
#: ../../../docs/faq.md:461
|
||||
msgid "You can freely create an issue for feature request on the repository at GitHub [here](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/new/choose). Note this is a community project with no financial backing, and there is not assurance that your request would be eventually picked up by others and the requested feature would become available. The easiest way to get a feature into this project is to just develop it yourself."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/faq.md:462
|
||||
#: ../../../docs/faq.md:463
|
||||
msgid "Also, please note that this playbook intends to focus solely on Matrix and Matrix-related services. If your request is not specific to Matrix, you may as well to consider to submit it to the [mash-playbook](https://github.com/mother-of-all-self-hosting/mash-playbook), maintained by the members behind this matrix-docker-ansible-deploy project. [This document on the interoperability](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/interoperability.md) describes how to deploy services along with the Matrix services easily."
|
||||
msgstr ""
|
||||
|
||||
Reference in New Issue
Block a user