mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-07-14 18:52:50 +03:00
Automatic translations update
This commit is contained in:
github-actions[bot]
committed by
GitHub
GitHub
parent
5a9e34c563
commit
38de158bad
+2309
-2261
File diff suppressed because it is too large
Load Diff
@@ -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-07-14 11:57+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"
|
||||
@@ -181,73 +181,81 @@ msgid "On the base domain's server (e.g. `example.com`), you can set up reverse-
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:115
|
||||
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 reverse-proxying, you **don't need** to add special HTTP headers for [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) reasons (like `Access-Control-Allow-Origin`), because your Matrix server (where requests ultimately go) will be configured by this playbook correctly."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:117
|
||||
msgid "If you use a 302 redirect instead, be aware that browsers apply CORS checks to every response in the redirect chain, so the redirect response itself must also carry an `Access-Control-Allow-Origin: *` header. Otherwise, web-based Matrix clients (like Element Web) may fail to work even though the final destination sets the header correctly."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:119
|
||||
msgid "**For nginx**, it would be something like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:134
|
||||
#: ../../../docs/configuring-well-known.md:136
|
||||
msgid "**For Apache2**, it would be something like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:148
|
||||
#: ../../../docs/configuring-well-known.md:150
|
||||
msgid "**For Caddy 2**, it would be something like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:158
|
||||
msgid "**For HAProxy**, it would be something like this:"
|
||||
#: ../../../docs/configuring-well-known.md:160
|
||||
msgid "**Note**: Caddy does not process directives in the order they appear in the Caddyfile, but according to its own [directive order](https://caddyserver.com/docs/caddyfile/directives#directive-order). Notably, `redir` is evaluated before `reverse_proxy`, so a `redir` elsewhere in the same site block (a common way to send the base domain to `www.example.com` or to another site) takes precedence and breaks the well-known reverse-proxying. In such cases, wrap the directives in [`handle`](https://caddyserver.com/docs/caddyfile/directives/handle) blocks to enforce the intended priority:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:177
|
||||
msgid "**For HAProxy**, it would be something like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:196
|
||||
msgid "**For Netlify**, configure a [redirect](https://docs.netlify.com/routing/redirects/) using a `_redirects` file in the [publish directory](https://docs.netlify.com/configure-builds/overview/#definitions) with contents like this:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:183
|
||||
#: ../../../docs/configuring-well-known.md:202
|
||||
msgid "**For AWS CloudFront**"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:185
|
||||
#: ../../../docs/configuring-well-known.md:204
|
||||
msgid "Add a custom origin with matrix.example.com to your distribution"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:186
|
||||
#: ../../../docs/configuring-well-known.md:205
|
||||
msgid "Add two behaviors, one for `.well-known/matrix/client` and one for `.well-known/matrix/server` and point them to your new origin."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:188
|
||||
#: ../../../docs/configuring-well-known.md:207
|
||||
msgid "Make sure to:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:190
|
||||
#: ../../../docs/configuring-well-known.md:209
|
||||
msgid "**replace `example.com`** in the server configuration with your actual domain name"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:191
|
||||
#: ../../../docs/configuring-well-known.md:210
|
||||
msgid "and: to **do this for the HTTPS-enabled server block**, as that's where Matrix expects the file to be"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:193
|
||||
#: ../../../docs/configuring-well-known.md:212
|
||||
msgid "Confirming it works"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:195
|
||||
#: ../../../docs/configuring-well-known.md:214
|
||||
msgid "No matter which method you've used to set up the well-known files, if you've done it correctly you should be able to see a JSON file at these URLs:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:197
|
||||
#: ../../../docs/configuring-well-known.md:216
|
||||
msgid "`https://example.com/.well-known/matrix/server`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:198
|
||||
#: ../../../docs/configuring-well-known.md:217
|
||||
msgid "`https://example.com/.well-known/matrix/client`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:199
|
||||
#: ../../../docs/configuring-well-known.md:218
|
||||
msgid "`https://example.com/.well-known/matrix/support`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/configuring-well-known.md:201
|
||||
#: ../../../docs/configuring-well-known.md:220
|
||||
msgid "You can also check if everything is configured correctly, by [checking if services work](maintenance-and-troubleshooting.md#how-to-check-if-services-work)."
|
||||
msgstr ""
|
||||
|
||||
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: matrix-docker-ansible-deploy \n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
|
||||
"POT-Creation-Date: 2026-07-14 11:57+0000\n"
|
||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
||||
"Language-Team: LANGUAGE <LL@li.org>\n"
|
||||
@@ -25,7 +25,7 @@ msgid "You can manually import your database from a previous default installatio
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:14
|
||||
#: ../../../docs/importing-postgres.md:38
|
||||
#: ../../../docs/importing-postgres.md:43
|
||||
msgid "**Notes**:"
|
||||
msgstr ""
|
||||
|
||||
@@ -57,98 +57,106 @@ msgstr ""
|
||||
msgid "Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:28
|
||||
#: ../../../docs/importing-postgres.md:29
|
||||
msgid "Do not import into a database that already contains tables (e.g. one that a service has already initialized and used). As the [official Synapse backup guide](https://element-hq.github.io/synapse/latest/usage/administration/backups.html) puts it: at best this will error, at worst it will lead to subtle database inconsistencies. Import into an empty (freshly created) database instead."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:31
|
||||
msgid "**Note for Synapse users restoring an older backup**: if the server kept running (and users kept chatting) after the backup you are restoring was made, truncate the `e2e_one_time_keys_json` table after importing and before starting Synapse. Restoring an older backup can otherwise cause already-used one-time keys to be re-issued, leading to message decryption errors for your users. You can do this by [getting a database terminal](maintenance-postgres.md#getting-a-database-terminal), connecting to the Synapse database (`\\c synapse`) and running `TRUNCATE e2e_one_time_keys_json;`. Clients will generate and upload fresh one-time keys automatically."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:33
|
||||
msgid "Importing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:30
|
||||
#: ../../../docs/importing-postgres.md:35
|
||||
msgid "To import, run this command (make sure to replace `SERVER_PATH_TO_POSTGRES_DUMP_FILE` with a file path on your server):"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:40
|
||||
#: ../../../docs/importing-postgres.md:45
|
||||
msgid "`SERVER_PATH_TO_POSTGRES_DUMP_FILE` must be a file path to a Postgres dump file on the server (not on your local machine!)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:41
|
||||
#: ../../../docs/importing-postgres.md:46
|
||||
msgid "`postgres_default_import_database` defaults to `matrix`, which is useful for importing multiple databases (for dumps made with `pg_dumpall`). If you're importing a single database (e.g. `synapse`), consider changing `postgres_default_import_database` accordingly"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:42
|
||||
#: ../../../docs/importing-postgres.md:47
|
||||
msgid "after importing a large database, it's a good idea to run [an `ANALYZE` operation](https://www.postgresql.org/docs/current/sql-analyze.html) to make Postgres rebuild its database statistics and optimize its query planner. You can easily do this via the playbook by running `just run-tags run-postgres-vacuum -e postgres_vacuum_preset=analyze` (see [Vacuuming PostgreSQL](maintenance-postgres.md#vacuuming-postgresql) for more details)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:44
|
||||
#: ../../../docs/importing-postgres.md:49
|
||||
msgid "Troubleshooting"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:46
|
||||
#: ../../../docs/importing-postgres.md:51
|
||||
msgid "Table Ownership"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:48
|
||||
#: ../../../docs/importing-postgres.md:53
|
||||
msgid "A table ownership issue can occur if you are importing from a Synapse installation which was both:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:50
|
||||
#: ../../../docs/importing-postgres.md:55
|
||||
msgid "migrated from SQLite to Postgres, and"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:51
|
||||
#: ../../../docs/importing-postgres.md:56
|
||||
msgid "used a username other than 'synapse'"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:53
|
||||
#: ../../../docs/importing-postgres.md:58
|
||||
msgid "In this case you may run into the following error during the import task:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:59
|
||||
#: ../../../docs/importing-postgres.md:64
|
||||
msgid "where `synapse_user` is the database username from the previous Synapse installation."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:61
|
||||
#: ../../../docs/importing-postgres.md:66
|
||||
msgid "This can be verified by examining the dump for ALTER TABLE statements which set OWNER TO that username:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:73
|
||||
#: ../../../docs/importing-postgres.md:78
|
||||
msgid "It can be worked around by changing the username to `synapse`, for example by using `sed`:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:79
|
||||
#: ../../../docs/importing-postgres.md:84
|
||||
msgid "This uses sed to perform an 'in-place' (`-i`) replacement globally (`/g`), searching for `synapse_user` and replacing with `synapse` (`s/synapse_user/synapse`). If your database username was different, change `synapse_user` to that username instead. Expand search/replace statement as shown in example above, in case of old user name like `matrix` — replacing `matrix` only would… well — you can imagine."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:81
|
||||
#: ../../../docs/importing-postgres.md:86
|
||||
msgid "Note that if the previous import failed with an error it may have made changes which are incompatible with re-running the import task right away; if you do so it may fail with an error such as:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:87
|
||||
#: ../../../docs/importing-postgres.md:92
|
||||
msgid "Repeat import"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:89
|
||||
#: ../../../docs/importing-postgres.md:94
|
||||
msgid "In this case you can use the command suggested in the import task to clear the database before retrying the import:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:97
|
||||
#: ../../../docs/importing-postgres.md:102
|
||||
msgid "Now on your local machine run `just run-tags setup-postgres` to prepare the database roles etc."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:99
|
||||
#: ../../../docs/importing-postgres.md:104
|
||||
msgid "If not, you probably get this error. `synapse` is the correct table owner, but the role is missing in database."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:105
|
||||
#: ../../../docs/importing-postgres.md:110
|
||||
msgid "Once the database is clear and the ownership of the tables has been fixed in the SQL file, the import task should succeed."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:107
|
||||
#: ../../../docs/importing-postgres.md:112
|
||||
msgid "Check, if `--dbname` is set to `synapse` (not `matrix`) and replace paths (or even better, copy this line from your terminal)"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:113
|
||||
#: ../../../docs/importing-postgres.md:118
|
||||
msgid "Hints"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-postgres.md:115
|
||||
#: ../../../docs/importing-postgres.md:120
|
||||
msgid "To open psql terminal run `/matrix/postgres/bin/cli`"
|
||||
msgstr ""
|
||||
|
||||
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: matrix-docker-ansible-deploy \n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2026-02-13 10:32+0000\n"
|
||||
"POT-Creation-Date: 2026-07-14 11:57+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"
|
||||
@@ -33,25 +33,29 @@ msgid "Before doing the actual data restore, **you need to upload your media sto
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-synapse-media-store.md:16
|
||||
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 "You also need the [rsync](https://rsync.samba.org/) utility installed **on the server**, as the import performs a server-side `rsync` synchronization. The playbook does not install it for you. On most distributions, it is available as a package called `rsync`."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-synapse-media-store.md:18
|
||||
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 "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:20
|
||||
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 "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:22
|
||||
msgid "Importing"
|
||||
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:24
|
||||
msgid "Importing"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-synapse-media-store.md:26
|
||||
msgid "Run this command (make sure to replace `<server-path-to-media_store>` with a path on your server):"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/importing-synapse-media-store.md:30
|
||||
#: ../../../docs/importing-synapse-media-store.md:32
|
||||
msgid "**Note**: `<server-path-to-media_store>` must be a file path to a `media_store` directory on the server (not on your local machine!)."
|
||||
msgstr ""
|
||||
|
||||
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: matrix-docker-ansible-deploy \n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2026-05-19 07:40+0000\n"
|
||||
"POT-Creation-Date: 2026-07-14 11:57+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"
|
||||
@@ -149,69 +149,73 @@ msgid "Restoring a backup made this way can be done by [importing it](importing-
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:79
|
||||
msgid "Upgrading PostgreSQL"
|
||||
msgid "**Note for Synapse users**: the [official Synapse backup guide](https://element-hq.github.io/synapse/latest/usage/administration/backups.html) recommends that the `e2e_one_time_keys_json` table either not be backed up, or be truncated after restoring (before Synapse is started). The full-server dump command above does include it, so if you ever restore a backup that is older than the server's current state, remember to truncate that table as described in [the importing guide](importing-postgres.md)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:81
|
||||
msgid "Unless you are using an [external Postgres server](configuring-playbook-external-postgres.md), this playbook initially installs Postgres for you."
|
||||
msgid "Upgrading PostgreSQL"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:83
|
||||
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 "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:85
|
||||
msgid "Upgrades must be performed manually."
|
||||
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:87
|
||||
msgid "Upgrades must be performed manually."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:89
|
||||
msgid "The playbook can upgrade your existing Postgres setup with the following command:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:93
|
||||
#: ../../../docs/maintenance-postgres.md:95
|
||||
msgid "**The old Postgres data directory is backed up** automatically, by renaming it to `/matrix/postgres/data-auto-upgrade-backup`. To rename to a different path, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_auto_upgrade_backup_data_path=/another/disk/matrix-postgres-before-upgrade\"`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:95
|
||||
#: ../../../docs/maintenance-postgres.md:97
|
||||
msgid "The auto-upgrade-backup directory stays around forever, until you **manually decide to delete it**."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:97
|
||||
#: ../../../docs/maintenance-postgres.md:99
|
||||
msgid "As part of the upgrade, the database is dumped to `/tmp`, an upgraded and empty Postgres server is started, and then the dump is restored into the new server. To use a different directory for the dump, pass some extra flags to the command above, like this: `--extra-vars=\"postgres_dump_dir=/directory/to/dump/here\"`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:99
|
||||
#: ../../../docs/maintenance-postgres.md:101
|
||||
msgid "To save disk space in `/tmp`, the dump file is gzipped on the fly at the expense of CPU usage. If you have plenty of space in `/tmp` and would rather avoid gzipping, you can explicitly pass a dump filename which doesn't end in `.gz`. Example: `--extra-vars=\"postgres_dump_name=matrix-postgres-dump.sql\"`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:101
|
||||
#: ../../../docs/maintenance-postgres.md:103
|
||||
msgid "**All databases, roles, etc. on the Postgres server are migrated**. However, other components that depend on specific Postgres versions (like the [Postgres Backup](configuring-playbook-postgres-backup.md) service) may need to be updated after the upgrade by using `just install-all`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:103
|
||||
#: ../../../docs/maintenance-postgres.md:105
|
||||
msgid "Tuning PostgreSQL"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:105
|
||||
#: ../../../docs/maintenance-postgres.md:107
|
||||
msgid "PostgreSQL can be [tuned](https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server) to make it run faster. This is done by passing extra arguments to the Postgres process."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:107
|
||||
#: ../../../docs/maintenance-postgres.md:109
|
||||
msgid "The [Postgres Ansible role](https://github.com/mother-of-all-self-hosting/ansible-role-postgres) **already does some tuning by default**, which matches the [tuning logic](https://github.com/le0pard/pgtune/blob/master/src/features/configuration/configurationSlice.js) done by websites like https://pgtune.leopard.in.ua/. You can manually influence some of the tuning variables. These parameters (variables) are injected via the `postgres_postgres_process_extra_arguments_default` variable."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:109
|
||||
#: ../../../docs/maintenance-postgres.md:111
|
||||
msgid "Most users should be fine with the automatically-done tuning. However, you may wish to:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:111
|
||||
#: ../../../docs/maintenance-postgres.md:113
|
||||
msgid "**adjust the automatically-determined tuning parameters manually**: change the values for the tuning variables defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) (see `postgres_max_connections`, `postgres_data_storage` etc). These variables are ultimately passed to Postgres via a `postgres_postgres_process_extra_arguments_default` variable"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:113
|
||||
#: ../../../docs/maintenance-postgres.md:115
|
||||
msgid "**turn automatically-performed tuning off**: override it like this: `postgres_postgres_process_extra_arguments_default: []`"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-postgres.md:115
|
||||
#: ../../../docs/maintenance-postgres.md:117
|
||||
msgid "**add additional tuning parameters**: define your additional Postgres configuration parameters in `postgres_postgres_process_extra_arguments_custom`. See `postgres_postgres_process_extra_arguments_default` defined in the Postgres role's [default configuration file](https://github.com/mother-of-all-self-hosting/ansible-role-postgres/blob/main/defaults/main.yml) for inspiration"
|
||||
msgstr ""
|
||||
|
||||
@@ -8,7 +8,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: matrix-docker-ansible-deploy \n"
|
||||
"Report-Msgid-Bugs-To: \n"
|
||||
"POT-Creation-Date: 2026-05-19 07:40+0000\n"
|
||||
"POT-Creation-Date: 2026-07-14 11:57+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"
|
||||
@@ -192,14 +192,18 @@ msgstr ""
|
||||
msgid "You can **learn more about cache-autotuning and the global cache factor settings** in the [Synapse's documentation on caches and associated values](https://matrix-org.github.io/synapse/latest/usage/configuration/config_documentation.html#caches-and-associated-values)."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-synapse.md:108
|
||||
#: ../../../docs/maintenance-synapse.md:109
|
||||
msgid "These limits apply **per Synapse process**. If you have [workers](configuring-playbook-synapse.md#load-balancing-with-workers) enabled, the main process and every worker each apply the configured limits independently, so the theoretical aggregate cache memory usage gets multiplied by the number of processes. When running many workers on a memory-constrained server, consider setting these variables to lower, explicitly chosen values."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-synapse.md:111
|
||||
msgid "To **disable cache auto-tuning**, unset all values:"
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-synapse.md:116
|
||||
#: ../../../docs/maintenance-synapse.md:119
|
||||
msgid "Users who wish to lower Synapse's RAM footprint should look into lowering the global cache factor and tweaking the autotune variables (or disabling auto-tuning). If your cache factor is too low for a given auto tune setting your caches will not reach autotune thresholds and autotune won't be able to do its job. Therefore, when auto-tuning is enabled (which it is by default), it's recommended to have your cache factor be large."
|
||||
msgstr ""
|
||||
|
||||
#: ../../../docs/maintenance-synapse.md:118
|
||||
#: ../../../docs/maintenance-synapse.md:121
|
||||
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 ""
|
||||
|
||||
Reference in New Issue
Block a user