This shall indicate that the public url of maubot is here configured the same as matrix_server_fqn_matrix but this must not be the case.
In the config I used the matrix fqnd directly as this part of the config is directly bound to the homeserver we want to connect to (but can not use the internal)

The /data is hardcoded in the container

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

> Error:   19:3      error    wrong indentation: expected 4 but found 2  (indentation)

Fixup for ba51997f7b

We redefine these variables in `group_vars/matrix_servers`, but it's better
to have some defaults in the role as well.

Currently, Synapse workers ignore the X-Forwarded headers, which leads to internal Docker IP addresses randomly appearing in the users' device list.

This adds the `x_forwarded: true` option to the worker config, fixing the issue.

Fixup for 5eff67371d - https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1884

matrix-corporal 2.3.0 supports Synapse v1.61.0 (which removed
communities/groups support).

Based on mautrix-whatsapp, as that's what the bridge software is based on.

Debug logs are inappropriate for production use.

Fixes #1873

The same logs still go to the systemd journal.

Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1864

Related to https://github.com/zeratax/matrix-registration/issues/93

This is a poor way to do things though. It may break again in the future.
matrix-registration is a poorly maintained project and should likely be removed from the playbook.