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

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2018-2025, 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: 2025-11-06 23:09+0900\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-element-admin.md:8
msgid "Setting up Element Admin (optional)"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:10
msgid "The playbook can install and configure [Element Admin](https://github.com/element-hq/element-admin) for you."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:12
msgid "Element Admin is a web-based administration panel for Synapse and [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md)."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:14
msgid "See the project's [documentation](https://github.com/element-hq/element-admin) to learn more."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:16
msgid "💡 **Note**: This project is still very young and doesn't have many features. For now, it's recommended to use [Synapse Admin](./configuring-playbook-synapse-admin.md) instead. Deployments that use [Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) can use Element Admin for user-management (something that Synapse Admin can't do), while continuing to use Synapse Admin for all other purposes."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:18
msgid "Prerequisites"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:20
msgid "A [Synapse](configuring-playbook-synapse.md) homeserver with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:21
msgid "[Matrix Authentication Service](./configuring-playbook-matrix-authentication-service.md) with its Admin API enabled (the playbook automatically enables it for you when you enable Element Admin)"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:23
msgid "Decide on a domain and path"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:25
msgid "By default, the Element Admin is configured to be served on the `admin.element.example.com` domain."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:27
msgid "If you'd like to run Element Admin on another hostname, see the [Adjusting the Element Admin URL](#adjusting-the-element-admin-url-optional) section below."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:29
msgid "Adjusting DNS records (optional)"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:31
msgid "By default, this playbook installs Element Admin on the `admin.element.` subdomain (`admin.element.example.com`) and requires you to create a `CNAME` record for `admin.element`, which targets `matrix.example.com`."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:33
msgid "When setting these values, replace `example.com` with your own."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:35
msgid "Adjusting the playbook configuration"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:37
msgid "Add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file:"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:43
msgid "Adjusting the Element Admin URL (optional)"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:45
msgid "By tweaking the `matrix_element_admin_hostname` variable, you can easily make the service available at a **different hostname** than the default one."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:47
msgid "Example additional configuration for your `vars.yml` file:"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:53
msgid "[!WARNING] A `matrix_element_admin_path_prefix` variable is also available and mean to let you configure a path prefix for the Element Admin service, but **Element Admin does not support running under a sub-path yet**."
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:56
msgid "Installing"
msgstr ""

#: ../../../docs/configuring-playbook-element-admin.md:58
msgid "After configuring the playbook and potentially [adjusting your DNS records](#adjusting-dns-records), run the playbook with [playbook tags](playbook-tags.md) as below:"
msgstr ""

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

#: ../../../docs/configuring-playbook-element-admin.md:67
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 ""