mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-07-13 18:31:11 +03:00
Automatic translations update
This commit is contained in:
github-actions[bot]
committed by
GitHub
GitHub
parent
90d486c4f6
commit
f8ed7fa855
@@ -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-13 13:36+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-13 13:36+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 ""
|
||||
|
||||
Reference in New Issue
Block a user