matrix-docker-ansible-deploy/examples/host-vars.yml

# This is something which is provided to Let's Encrypt
# when retrieving the SSL certificates for `<your-domain>`.
#
# In case SSL renewal fails at some point, you'll also get
# an email notification there.
#
# Example value: someone@example.com
host_specific_matrix_ssl_support_email: YOUR_EMAIL_ADDRESS_HERE

# This is your bare domain name (`<your-domain`).
#
# Note: the server specified here is not touched.
#
# This playbook only installs to `matrix.<your-domain>`,
# but it nevertheless requires to know the bare domain name
# (for configuration purposes).
#
# Example value: example.com
host_specific_hostname_identity: YOUR_BARE_DOMAIN_NAME_HERE

# A shared secret (between Synapse and Coturn) used for authentication.
# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
matrix_coturn_turn_static_auth_secret: ""

# A secret used to protect access keys issued by the server.
# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
matrix_synapse_macaroon_secret_key: ""
Initial commit 2017-07-31 22:07:30 +02:00			`# This is something which is provided to Let's Encrypt`
			# when retrieving the SSL certificates for `<your-domain>`.
			`#`
			`# In case SSL renewal fails at some point, you'll also get`
			`# an email notification there.`
			`#`
			`# Example value: someone@example.com`
Move SSL certificates from /etc/pki/acmetool-certs to /matrix/ssl Moving keeps everything in the /matrix directory, so that we wouldn't contaminate anything else on the system or risk clashing with something else. Also retrieving certificates separately for the Riot and Matrix domains, which should help in multiple ways: - allows them to be very different (completely separate base domain..) - allows for Riot to be disabled for the playbook some time later and still have the code not break 2017-09-11 22:50:14 +02:00			`host_specific_matrix_ssl_support_email: YOUR_EMAIL_ADDRESS_HERE`
Initial commit 2017-07-31 22:07:30 +02:00
			# This is your bare domain name (`<your-domain`).
			`#`
			`# Note: the server specified here is not touched.`
			`#`
			# This playbook only installs to `matrix.<your-domain>`,
			`# but it nevertheless requires to know the bare domain name`
			`# (for configuration purposes).`
			`#`
			`# Example value: example.com`
Switch Docker image to official one Switching from from avhost/docker-matrix (silviof/docker-matrix) to matrixdotorg/synapse. The avhost/docker-matrix (silviof/docker-matrix) image used to bundle in the coturn STUN/TURN server, so as part of the move, we're separating this to a separately-ran service (matrix-coturn.service, powered by instrumentisto/coturn-docker-image) 2018-05-25 20:58:53 +02:00			`host_specific_hostname_identity: YOUR_BARE_DOMAIN_NAME_HERE`

			`# A shared secret (between Synapse and Coturn) used for authentication.`
			# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
Set up Synapse configuration using a template (not line/regexp replacements) Until now, we were starting from a fresh configuration, as generated by Synapse and manipulating it with regex and line replacements, until we made it work. This is more fragile and less predictable, so we're moving to a static configuration file generated from a Jinja template. The upside is that configuration will be stable and predictable. The downside of this new approach is that any manual configuration changes after the playbook is done, will be thrown away on future playbook invocations. There are 2 ways to work around the need for manual configuration changes though: - making them part of this playbook and its default template configuration files (which benefits everyone) - going your own way for a given host and overriding the template files that gets used (that is, the `matrix_synapse_template_synapse_homeserver` or `matrix_synapse_template_synapse_log` variables) 2018-06-26 20:05:59 +02:00			`matrix_coturn_turn_static_auth_secret: ""`

			`# A secret used to protect access keys issued by the server.`
			# You can put any string here, but generating a strong one is preferred (e.g. `pwgen -s 64 1`).
Add mautrix-telegram to bridge with telegram services 2018-09-01 17:51:07 +02:00			`matrix_synapse_macaroon_secret_key: ""`