Wiring happens via `group_vars/matrix_servers` now.

It's the same result as b6d45304b4b19, but it's done in a cleaner way.

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

.. and try to auto-switch between `bind` and `volume` depending on
whether there's a slash in the `src` path.

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

Added link to exim/email documentation

update postmoogle 0.9.13 -> 0.9.14

Related to 6a52be7987 and 28e7ef9c71f02

* make banlist consistent
* proper multi-error message
* ignore "." MX hosts
* try recipient domain directly, even when MX records found, but failed

Update synapse 1.76.0 -> 1.77.0

Update hydrogen 0.3.7 -> 0.3.8

Bump element version

Signed-off-by: Julian-Samuel Gebühr <julian-samuel@gebuehr.net>

Previously, it had to go through matrix-nginx-proxy.
It's exposed to Traefik directly via container labels now

Previously, it had to go through matrix-nginx-proxy.
It's exposed to Traefik directly via container labels now

Serving at a path other than `/` doesn't work well yet.

We were mounting our own configuration to
`/usr/share/nginx/html/config.json`, which is a symlink to
`/tmp/config.json`. So we effectively mount our file to
`/tmp/config.json`.

When starting:

- if Hydrogen sees a `CONFIG_OVERRIDE` environment variable,
  it will try to save it into our read-only config file and fail.

- if Hydrogen doesn't see a `CONFIG_OVERRIDE` environment variable (the
  path we go through, because we don't pass such a variable),
  it will try to copy its bundled configuration (`/config.json.bundled`)
  to `/tmp/config.json`. Because our configuration is mounted as read-only, it will
  fail.

In both cases, it will fail with:

> cp: can't create '/tmp/config.json': File exists

Source: 3720de36bb/docker/dynamic-config.sh

We work around this by mounting our configuration on top of the bundled
one (`/config.json.bundled`). We then let Hydrogen's startup script copy
it to `/tmp/config.json` (a tmpfs we've mounted into the container) and use it from there.

This may proof useful to someone in the future.

We've had it on `matrix-nginx-proxy` before, but
our initial support for Traefik did not include any of these security
headers.

Previously, we had to run it at a subpath, like `/synapse-admin`.

We can now dedicate a whole domain and the `/` path to it, should we
wish to do so.

Previously, it had to go through matrix-nginx-proxy.
It's exposed to Traefik directly via container labels now

Update postmoogle 0.9.12 -> 0.9.13

Regression since 3d9aa8387e

* live SSL certificates reload on file changes (e.g., on automatic certs renewal)
* print all errors when trying connection to an SMTP server

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

Seems like this affected all "own webserver" deployments, which required
port exposure.

`playbook-managed-traefik` and `playbook-managed-nginx` were not affected.

Update coturn 4.6.1-r1 -> 4.6.1-r2

Previously, it had to go through matrix-nginx-proxy.
It's exposed to Traefik directly via container labels now.

Referenced here: 06f5be4fa5 (r100414988)

restore borg prefixes

Supersedes https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2472

It's probably unnecessary, as this user is only used in the borg container
internally, but.. It doesn't hurt to set it to `matrix`.