For example, synapse-admin connects to additional networks here:
c0559870b5/roles/custom/matrix-synapse-admin/templates/systemd/matrix-synapse-admin.service.j2 (L39-L41)

This defaults to 'traefik' through
matrix_playbook_reverse_proxy_container_network, which is not correct in
case matrix_playbook_reverse_proxy_type is set to none.

* Add logout_redirect_url var and option templating for matrix element client

* Simplify logout_redirect_url templating and make it safer

Using `to_json` to make it safer.

Judging by the code here 0b24d33c64/src/Lifecycle.ts (L1026-L1032)
it doesn't seem like it leaving `logout_redirect_url` empty will hurt, so this patch removes the `if` block.

* Add comment for the `matrix_client_element_logout_redirect_url` variable

---------

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

We were overriding the `matrix_bot_matrix_registration_bot_matrix_homeserver_url` variable via `group_vars/matrix_servers`
to point it to the container-local homeserver URL, but this variable was not being used at all.

The actual variable name (which was being used) is `matrix_bot_matrix_registration_bot_api_base_url`.

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

Possibly fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3900

This patch hasn't been tested.

Provoked by https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3900

Provoked by https://github.com/etkecc/mrs/pull/4
I've discovered that Cinny supports various configuration options and it'd be better
if we add support for them.

Fixup for 784a5aaef4.

We do not let bridges update config files, so generation cannot happen.
We don't want the bridge to manage the config file anyway.

Ref: https://matrix-org.github.io/matrix-hookshot/latest/advanced/encryption.html#enabling-encryption-in-hookshot

> To fix such issues, stop Hookshot, then reset its crypto store by running yarn start:resetcrypto.

Somewhat related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3868

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

Related to https://github.com/matrix-org/matrix-hookshot/issues/730

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3863

As using `@alice` and `@bob` on this context is confusing, this commit replaces them with `@email2matrix1` and `@email2matrix2`, respectively.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

From `@<username>`, `@your_username`, `@example`, etc.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

* set localpart of hookshot bot in main.yml

* set sender_localpart in registration.yml.j2 template to variable

* prettier location for bot localpart in main.yml

* Update main.yml

* Update registration.yml.j2

---------

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

We used to pass the shared secret for double-puppeting via a
`login_shared_secret` parameter, which doesn't seem to exist anymore.
The proper way to do it is via `login_shared_secret_map`.

The comments for `login_shared_secret_map` seem to indicate that it's
only usable with the shared-secret-auth password provider.

However, this bridge is based on mautrix-python (`>=0.20.5,<0.21`) as
per its `requirements.txt`
Support for double-puppeting via arbitrary access tokens landed in
mautrix-python 0.20.1 (6f25b62e80/CHANGELOG.md (L44-L53),)
so it should be possible to use appservice double-puppet.
Related to af04ca1238

A bunch of other parameters seem to have moved around as well.

This patch introduces some new Ansible variables for controlling
additional settings related to encryption, etc.