(yes, a bit awkward and brittle… xD)

also, worker.yaml.j2:
  - hone worker_name
  - remove worker_pid_file entry (would only be used if worker_daemonize
    set to true; also, synapse only knows about the container namespace
    and thus can not provide the required host-view PID)

add variables for secure_backup_required and secure_backup_setup_methods

Discussed in #669 (Github Issue).

Upgrade Element (1.7.8 -> 1.7.9)

Update nginx (1.19.2 -> 1.19.3)

Shameless refactor of all systemd descriptions for bridges

Upgrade Synapse (v1.20.1 -> v1.21.0)

Add docker prune

& restrict federation listener; frontend_proxy / user_dir don't need it

.. alphabetically and put those not documented as multi-instance
capable on ports ending on zero.

Is the PID magic gonna work? or will it need an ExecStartPost hack..

- cherry-pick "Ensure worker config exists in systemd service (#7528)"
  from synapse d74cdc1a42e8b487d74c214b1d0ca575429d546a:
  "check that the worker config file exists instead of silently failing."

If the SQLite database was from an older version of Synapse, it appears
that Synapse would try to run migrations on it first, before importing.
This was failing, because the file wasn't writable.

Hopefully, this fixes the problem.

Adding '.python-version' to .gitignore

caddy2: removed unknown tls directive

Use up-to-date PostgreSQL container version for backups.

Related to 23daec748c and #662 (Github Issue).

Interestingly, no one has reported this failure before #662 (Github
Issue).

It doesn't make sense to keep saying that we support such old Ansible
versions, when we're not even testing on anything close to those.

Time is also passing and such versions are getting more and more
ancient. It's time we bumped our requirements to something that is more
likely to work.

Element web : update welcome page template

Add support for postgres 13