self-hosted/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-12-12 08:43:55 +02:00
Code Issues Releases Activity
9b5be6825d
matrix-docker-ansible-deploy/docs/configuring-playbook-riot-web.md
Slavi Pantaleev e81a395a98 Drop some matrix_nginx_proxy_proxy_riot_compat_* variables 
matrix-nginx-proxy is going away and this is one of the features it
offered.

This feature will have no equivalent in our new Traefik-only
setup, although it's possible to implement it manually by using
`matrix_client_element_container_labels_additional_labels`
2024-01-03 14:43:45 +02:00

1.7 KiB
Raw Blame History

Configuring Riot-web (optional)

By default, this playbook used to install the Riot-web Matrix client web application.

Riot has since been renamed to Element.

Migrating to Element

Migrating your custom settings

If you have custom matrix_riot_web_ variables in your inventory/host_vars/matrix.DOMAIN/vars.yml file, you'll need to rename them (matrix_riot_web_ -> matrix_client_element_).

Some other playbook variables (but not all) with riot in their name are also renamed. The playbook checks and warns if you are using the old name for some commonly used ones.

Domain migration

We used to set up Riot at the riot.DOMAIN domain. The playbook now sets up Element at element.DOMAIN by default.

There are a few options for handling this:

  • (avoiding changes - using the old riot.DOMAIN domain and avoiding DNS changes) -- to keep using riot.DOMAIN instead of element.DOMAIN, override the domain at which the playbook serves Element: matrix_server_fqn_element: "riot.{{ matrix_domain }}"

  • (embracing changes - using only element.DOMAIN) - set up the element.DOMAIN DNS record (see Configuring DNS). You can drop the riot.DOMAIN in this case.

Re-running the playbook

As always, after making the necessary DNS and configuration adjustments, re-run the playbook to apply the changes.