Matrix Docker Ansible eploy
Nevar pievienot vairāk kā 25 tēmas Tēmai ir jāsākas ar burtu vai ciparu, tā var saturēt domu zīmes ('-') un var būt līdz 35 simboliem gara.
 
 

134 rindas
7.5 KiB

  1. # SOME DESCRIPTIVE TITLE.
  2. # Copyright (C) 2018-2026, Slavi Pantaleev, Aine Etke, MDAD community members
  3. # This file is distributed under the same license as the matrix-docker-ansible-deploy package.
  4. # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
  5. #
  6. #, fuzzy
  7. msgid ""
  8. msgstr ""
  9. "Project-Id-Version: matrix-docker-ansible-deploy \n"
  10. "Report-Msgid-Bugs-To: \n"
  11. "POT-Creation-Date: 2026-02-13 10:32+0000\n"
  12. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
  13. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
  14. "Language-Team: LANGUAGE <LL@li.org>\n"
  15. "MIME-Version: 1.0\n"
  16. "Content-Type: text/plain; charset=UTF-8\n"
  17. "Content-Transfer-Encoding: 8bit\n"
  18. #: ../../../docs/configuring-playbook-ssl-certificates.md:12
  19. msgid "Adjusting SSL certificate retrieval (optional, advanced)"
  20. msgstr ""
  21. #: ../../../docs/configuring-playbook-ssl-certificates.md:14
  22. msgid "By default, the playbook retrieves and automatically renews free SSL certificates from [Let's Encrypt](https://letsencrypt.org/) via [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) for the domains of the services it installs (e.g. `matrix.example.com` and others). Refer this guide if you want to modify settings about how it manages SSL certificates or have the Traefik server use yours."
  23. msgstr ""
  24. #: ../../../docs/configuring-playbook-ssl-certificates.md:16
  25. msgid "**Notes**:"
  26. msgstr ""
  27. #: ../../../docs/configuring-playbook-ssl-certificates.md:17
  28. msgid "This guide is intended to be referred for configuring the integrated Traefik server with regard to SSL certificates retrieval. If you're using [your own webserver](configuring-playbook-own-webserver.md), consult its documentation about how to configure it."
  29. msgstr ""
  30. #: ../../../docs/configuring-playbook-ssl-certificates.md:18
  31. msgid "Let's Encrypt ends the expiration notification email service on June 4, 2025 (see: [the official announcement](https://letsencrypt.org/2025/01/22/ending-expiration-emails/)), and it recommends using a third party service for those who want to receive expiration notifications. If you are looking for a self-hosting service, you may be interested in a monitoring tool such as [Update Kuma](https://github.com/louislam/uptime-kuma/)."
  32. msgstr ""
  33. #: ../../../docs/configuring-playbook-ssl-certificates.md:20
  34. msgid "The [Mother-of-All-Self-Hosting (MASH)](https://github.com/mother-of-all-self-hosting/mash-playbook) Ansible playbook can be used to install and manage an Uptime Kuma instance. See [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/uptime-kuma.md) for the instruction to install it with the playbook. If you are wondering how to use it for your Matrix server, refer to [this page](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/setting-up-services-on-mdad-server.md) for the overview."
  35. msgstr ""
  36. #: ../../../docs/configuring-playbook-ssl-certificates.md:22
  37. msgid "Use staging Let's Encrypt certificates"
  38. msgstr ""
  39. #: ../../../docs/configuring-playbook-ssl-certificates.md:24
  40. msgid "For testing purposes, you may wish to use staging certificates provided by Let's Encrypt to avoid hitting [its rate limits](https://letsencrypt.org/docs/rate-limits/)."
  41. msgstr ""
  42. #: ../../../docs/configuring-playbook-ssl-certificates.md:26
  43. msgid "To use ones, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
  44. msgstr ""
  45. #: ../../../docs/configuring-playbook-ssl-certificates.md:32
  46. msgid "Disable SSL termination"
  47. msgstr ""
  48. #: ../../../docs/configuring-playbook-ssl-certificates.md:34
  49. msgid "For testing or other purposes, you may wish to install services without SSL termination and have services exposed to `http://` instead of `https://`."
  50. msgstr ""
  51. #: ../../../docs/configuring-playbook-ssl-certificates.md:36
  52. msgid "To do so, add the following configuration to your `vars.yml` file:"
  53. msgstr ""
  54. #: ../../../docs/configuring-playbook-ssl-certificates.md:42
  55. msgid "Use self-signed SSL certificates"
  56. msgstr ""
  57. #: ../../../docs/configuring-playbook-ssl-certificates.md:44
  58. msgid "To use self-signed certificates, generate them and follow the documentation below about using your own certificates."
  59. msgstr ""
  60. #: ../../../docs/configuring-playbook-ssl-certificates.md:46
  61. msgid "Use your own SSL certificates"
  62. msgstr ""
  63. #: ../../../docs/configuring-playbook-ssl-certificates.md:48
  64. msgid "To use your own certificates, prepare them and follow the steps below:"
  65. msgstr ""
  66. #: ../../../docs/configuring-playbook-ssl-certificates.md:50
  67. msgid "Disable [ACME](https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment) / [Let's Encrypt](https://letsencrypt.org/) support"
  68. msgstr ""
  69. #: ../../../docs/configuring-playbook-ssl-certificates.md:51
  70. 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"
  71. msgstr ""
  72. #: ../../../docs/configuring-playbook-ssl-certificates.md:52
  73. msgid "Register your custom configuration file with Traefik, by adding an extra provider of type [file](https://doc.traefik.io/traefik/providers/file/)"
  74. msgstr ""
  75. #: ../../../docs/configuring-playbook-ssl-certificates.md:53
  76. 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"
  77. msgstr ""
  78. #: ../../../docs/configuring-playbook-ssl-certificates.md:55
  79. msgid "For those steps, you can add the following configuration to your `vars.yml` file (adapt to your needs). If you will put the custom configuration files manually, make sure to remove the `aux_file_definitions` variable."
  80. msgstr ""
  81. #: ../../../docs/configuring-playbook-ssl-certificates.md:103
  82. msgid "Use a DNS-01 ACME challenge type, instead of HTTP-01"
  83. msgstr ""
  84. #: ../../../docs/configuring-playbook-ssl-certificates.md:105
  85. 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 can be helpful to:"
  86. msgstr ""
  87. #: ../../../docs/configuring-playbook-ssl-certificates.md:107
  88. msgid "hide your public IP from Let's Encrypt logs"
  89. msgstr ""
  90. #: ../../../docs/configuring-playbook-ssl-certificates.md:108
  91. 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)"
  92. msgstr ""
  93. #: ../../../docs/configuring-playbook-ssl-certificates.md:110
  94. msgid "Example: Cloudflare"
  95. msgstr ""
  96. #: ../../../docs/configuring-playbook-ssl-certificates.md:112
  97. msgid "Here is an example for configurations on the `vars.yml` file for Cloudflare. Please adjust it as necessary before applying it."
  98. msgstr ""
  99. #: ../../../docs/configuring-playbook-ssl-certificates.md:127
  100. 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)."
  101. msgstr ""
  102. #: ../../../docs/configuring-playbook-ssl-certificates.md:129
  103. 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."
  104. msgstr ""