matrix-docker-ansible-deploy/i18n/translation-templates/docs/configuring-playbook-dendrite.pot

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community members
# This file is distributed under the same license as the matrix-docker-ansible-deploy package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: matrix-docker-ansible-deploy \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-20 07:23+0200\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"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#: ../../../docs/configuring-playbook-dendrite.md:1
msgid "Configuring Dendrite (optional)"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:3
msgid "By default, this playbook configures the [Synapse](https://github.com/element-hq/synapse) Matrix server, but you can also use [Dendrite](https://github.com/matrix-org/dendrite)."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:5
msgid "**Notes**:"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:7
msgid "**You can't switch an existing Matrix server's implementation** (e.g. Synapse -> Dendrite). Proceed below only if you're OK with losing data or you're dealing with a server on a new domain name, which hasn't participated in the Matrix federation yet."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:9
msgid "**homeserver implementations other than Synapse may not be fully functional**. The playbook may also not assist you in an optimal way (like it does with Synapse). Make yourself familiar with the downsides before proceeding"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:11
msgid "Adjusting the playbook configuration"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:13
msgid "To use Dendrite, you **generally** need to add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:19
msgid "The playbook provides lots of customization variables you could use to change Dendrite's settings."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:21
msgid "Their defaults are defined in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml) and they ultimately end up in the generated `/matrix/dendrite/config/dendrite.yaml` file (on the server). This file is generated from the [`roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2) template."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:23
msgid "**If there's an existing variable** which controls a setting you wish to change, you can simply define that variable in your configuration file (`inventory/host_vars/matrix.example.com/vars.yml`) and [re-run the playbook](installing.md) to apply the changes."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:25
msgid "Alternatively, **if there is no pre-defined variable** for a Dendrite setting you wish to change:"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:27
msgid "you can either **request a variable to be created** (or you can submit such a contribution yourself). Keep in mind that it's **probably not a good idea** to create variables for each one of Dendrite's various settings that rarely get used."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:29
msgid "or, you can **extend and override the default configuration** ([`dendrite.yaml.j2`](../roles/custom/matrix-dendrite/templates/dendrite/dendrite.yaml.j2)) by making use of the `matrix_dendrite_configuration_extension_yaml` variable. You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:31
msgid "or, if extending the configuration is still not powerful enough for your needs, you can **override the configuration completely** using `matrix_dendrite_configuration` (or `matrix_dendrite_configuration_yaml`). You can find information about this in [`roles/custom/matrix-dendrite/defaults/main.yml`](../roles/custom/matrix-dendrite/defaults/main.yml)."
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:33
msgid "Installing"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:35
msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:42
msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-all` or `just setup-all`"
msgstr ""

#: ../../../docs/configuring-playbook-dendrite.md:44
msgid "`just install-all` is useful for maintaining your setup quickly ([2x-5x faster](../CHANGELOG.md#2x-5x-performance-improvements-in-playbook-runtime) than `just setup-all`) when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note these shortcuts run the `ensure-matrix-users-created` tag too."
msgstr ""