overmind
/
matrix-docker-ansible-deploy
ミラー元 https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
フォーク 0
コード 課題 0 リリース 0 Wiki アクティビティ
Matrix Docker Ansible eploy
選択できるのは25トピックまでです。 トピックは、先頭が英数字で、英数字とダッシュ('-')を使用した35文字以内のものにしてください。
10090 コミット
14 ブランチ
848 MiB
 
 
ツリー: ec00a76b14
ブランチ タグ
${ item.name }
ブランチ ${ searchTerm } を作成
'ec00a76b14' から
${ noResults }
matrix-docker-ansible-deploy/i18n/locales/bg/LC_MESSAGES/docs/howto-server-delegation.po

191 行
10 KiB
Raw Blame 履歴 

  1. # SOME DESCRIPTIVE TITLE.

  2. # Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community

  3. # members

  4. # This file is distributed under the same license as the

  5. # matrix-docker-ansible-deploy package.

  6. # FIRST AUTHOR <EMAIL@ADDRESS>, 2024.

  7. #

  8. #, fuzzy

  9. msgid ""

  10. msgstr ""

  11. "Project-Id-Version: matrix-docker-ansible-deploy \n"

  12. "Report-Msgid-Bugs-To: \n"

  13. "POT-Creation-Date: 2025-01-27 09:54+0200\n"

  14. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

  15. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

  16. "Language: bg\n"

  17. "Language-Team: bg <LL@li.org>\n"

  18. "Plural-Forms: nplurals=2; plural=(n != 1);\n"

  19. "MIME-Version: 1.0\n"

  20. "Content-Type: text/plain; charset=utf-8\n"

  21. "Content-Transfer-Encoding: 8bit\n"

  22. "Generated-By: Babel 2.16.0\n"

  23. 

  24. #: ../../../docs/howto-server-delegation.md:1

  25. msgid "Server Delegation"

  26. msgstr ""

  27. 

  28. #: ../../../docs/howto-server-delegation.md:3

  29. 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."

  30. msgstr ""

  31. 

  32. #: ../../../docs/howto-server-delegation.md:5

  33. msgid "Server delegation can be configured in either of these ways:"

  34. msgstr ""

  35. 

  36. #: ../../../docs/howto-server-delegation.md:7

  37. msgid "[Setting up a `/.well-known/matrix/server` file](#server-delegation-via-a-well-known-file) on the base domain (`example.com`)"

  38. msgstr ""

  39. 

  40. #: ../../../docs/howto-server-delegation.md:8

  41. msgid "[Setting up a `_matrix._tcp` DNS SRV record](#server-delegation-via-a-dns-srv-record-advanced)"

  42. msgstr ""

  43. 

  44. #: ../../../docs/howto-server-delegation.md:10

  45. msgid "Both methods have their place and will continue to do so. You only need to use just one of these delegation methods."

  46. msgstr ""

  47. 

  48. #: ../../../docs/howto-server-delegation.md:12

  49. 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."

  50. msgstr ""

  51. 

  52. #: ../../../docs/howto-server-delegation.md:14

  53. 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."

  54. msgstr ""

  55. 

  56. #: ../../../docs/howto-server-delegation.md:16

  57. msgid "Server Delegation via a well-known file"

  58. msgstr ""

  59. 

  60. #: ../../../docs/howto-server-delegation.md:18

  61. 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."

  62. msgstr ""

  63. 

  64. #: ../../../docs/howto-server-delegation.md:20

  65. 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)"

  66. msgstr ""

  67. 

  68. #: ../../../docs/howto-server-delegation.md:22

  69. msgid "Downsides of well-known-based Server Delegation"

  70. msgstr ""

  71. 

  72. #: ../../../docs/howto-server-delegation.md:24

  73. msgid "Server Delegation by means of a `/.well-known/matrix/server` file is the most straightforward, but suffers from the following downsides:"

  74. msgstr ""

  75. 

  76. #: ../../../docs/howto-server-delegation.md:26

  77. 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)."

  78. msgstr ""

  79. 

  80. #: ../../../docs/howto-server-delegation.md:28

  81. 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):"

  82. msgstr ""

  83. 

  84. #: ../../../docs/howto-server-delegation.md:30

  85. msgid "Errors are recommended to be cached for up to an hour, and servers are encouraged to exponentially back off for repeated failures."

  86. msgstr ""

  87. 

  88. #: ../../../docs/howto-server-delegation.md:32

  89. 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."

  90. msgstr ""

  91. 

  92. #: ../../../docs/howto-server-delegation.md:34

  93. 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)."

  94. msgstr ""

  95. 

  96. #: ../../../docs/howto-server-delegation.md:36

  97. msgid "Server Delegation via a DNS SRV record (advanced)"

  98. msgstr ""

  99. 

  100. #: ../../../docs/howto-server-delegation.md:38

  101. 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."

  102. msgstr ""

  103. 

  104. #: ../../../docs/howto-server-delegation.md:40

  105. 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)."

  106. msgstr ""

  107. 

  108. #: ../../../docs/howto-server-delegation.md:42

  109. msgid "This prevents you from suffering the [Downsides of well-known-based Server Delegation](#downsides-of-well-known-based-server-delegation)."

  110. msgstr ""

  111. 

  112. #: ../../../docs/howto-server-delegation.md:44

  113. msgid "To use DNS SRV record validation, you need to:"

  114. msgstr ""

  115. 

  116. #: ../../../docs/howto-server-delegation.md:46

  117. 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`."

  118. msgstr ""

  119. 

  120. #: ../../../docs/howto-server-delegation.md:48

  121. 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`"

  122. msgstr ""

  123. 

  124. #: ../../../docs/howto-server-delegation.md:50

  125. 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."

  126. msgstr ""

  127. 

  128. #: ../../../docs/howto-server-delegation.md:52

  129. 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)"

  130. msgstr ""

  131. 

  132. #: ../../../docs/howto-server-delegation.md:54

  133. msgid "Obtain certificates"

  134. msgstr ""

  135. 

  136. #: ../../../docs/howto-server-delegation.md:56

  137. msgid "How you can obtain a valid certificate for `example.com` on the `matrix.example.com` server is up to you."

  138. msgstr ""

  139. 

  140. #: ../../../docs/howto-server-delegation.md:58

  141. 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."

  142. msgstr ""

  143. 

  144. #: ../../../docs/howto-server-delegation.md:60

  145. 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."

  146. msgstr ""

  147. 

  148. #: ../../../docs/howto-server-delegation.md:62

  149. msgid "Serving the Federation API with your certificates"

  150. msgstr ""

  151. 

  152. #: ../../../docs/howto-server-delegation.md:64

  153. 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."

  154. msgstr ""

  155. 

  156. #: ../../../docs/howto-server-delegation.md:66

  157. msgid "Based on your setup, you have different ways to go about it:"

  158. msgstr ""

  159. 

  160. #: ../../../docs/howto-server-delegation.md:68

  161. msgid "Serving the Federation API with your certificates and Synapse handling Federation"

  162. msgstr ""

  163. 

  164. #: ../../../docs/howto-server-delegation.md:70

  165. msgid "You can let Synapse handle Federation by itself."

  166. msgstr ""

  167. 

  168. #: ../../../docs/howto-server-delegation.md:72

  169. msgid "To do that, make sure the certificate files are mounted into the Synapse container:"

  170. msgstr ""

  171. 

  172. #: ../../../docs/howto-server-delegation.md:79

  173. msgid "You can then tell Synapse to serve Federation traffic over TLS on `tcp/8448`:"

  174. msgstr ""

  175. 

  176. #: ../../../docs/howto-server-delegation.md:87

  177. 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."

  178. msgstr ""

  179. 

  180. #: ../../../docs/howto-server-delegation.md:89

  181. msgid "Serving the Federation API with your certificates and another webserver"

  182. msgstr ""

  183. 

  184. #: ../../../docs/howto-server-delegation.md:91

  185. 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."

  186. msgstr ""

  187. 

  188. #: ../../../docs/howto-server-delegation.md:93

  189. 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."

  190. msgstr ""