|
|
|
|
---
|
|
|
|
|
# The bare domain name which represents your Matrix identity.
|
|
|
|
|
# Matrix user ids for your server will be of the form (`@user:<matrix-domain>`).
|
|
|
|
|
#
|
|
|
|
|
# Note: this playbook does not touch the server referenced here.
|
|
|
|
|
# Installation happens on another server ("matrix.<matrix-domain>").
|
|
|
|
|
#
|
|
|
|
|
# If you've deployed using the wrong domain, you'll have to run the Uninstalling step,
|
|
|
|
|
# because you can't change the Domain after deployment.
|
|
|
|
|
#
|
|
|
|
|
# Example value: example.com
|
|
|
|
|
matrix_domain: YOUR_BARE_DOMAIN_NAME_HERE
|
|
|
|
|
|
|
|
|
|
# The Matrix homeserver software to install.
|
|
|
|
|
# See `roles/matrix-base/defaults/main.yml` for valid options.
|
|
|
|
|
matrix_homeserver_implementation: synapse
|
|
|
|
|
|
|
|
|
|
# A secret used as a base, for generating various other secrets.
|
|
|
|
|
# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
|
|
|
|
|
matrix_homeserver_generic_secret_key: ''
|
|
|
|
|
|
|
|
|
|
# This is something which is provided to Let's Encrypt when retrieving SSL certificates for domains.
|
|
|
|
|
#
|
|
|
|
|
# In case SSL renewal fails at some point, you'll also get an email notification there.
|
|
|
|
|
#
|
|
|
|
|
# If you decide to use another method for managing SSL certificates (different than the default Let's Encrypt),
|
|
|
|
|
# you won't be required to define this variable (see `docs/configuring-playbook-ssl-certificates.md`).
|
|
|
|
|
#
|
|
|
|
|
# Example value: someone@example.com
|
|
|
|
|
matrix_ssl_lets_encrypt_support_email: ''
|
|
|
|
|
|
|
|
|
|
# A Postgres password to use for the superuser Postgres user (called `matrix` by default).
|
|
|
|
|
#
|
|
|
|
|
# The playbook creates additional Postgres users and databases (one for each enabled service)
|
|
|
|
|
# using this superuser account.
|
|
|
|
|
matrix_postgres_connection_password: ''
|
