Caddy2 Caddyfile example and Comment in examples/host_vars.yml

Update configuring-playbook-jitsi.md

Changes matrix_dimension_integrations_ui_url from /riot to /element h…

PullRequest

Removes DS-Store

Fix links to using your own webserver doc

modified example for jitsi ldap authentication to show all available variables.

Related to #643 (Github Issue)

Change anonymized to general

Change anonymized to more proper term as server vice this is not anonymized. Server name is the first parameter that is collected. And if server happens to be for individual use these statistics would be at personal level without any anonymising.

This is mainly to address SSL renewal not working for us due to:
- https://github.com/ansible/ansible/issues/71213
- https://github.com/ansible/ansible/pull/71207

Using the cron module was hacky anyway. We shouldn't need an extra
level of buggy abstraction to manage a cronjob file.

Fixes #106 (Github Issue).

We recently had a report of the Postgres backup container's log file
growing the size of /var/lib/docker until it ran out of disk space.

Trying to prevent similar problems in the future.

Certain more-minimal Debian installations may not have
lsb-release installed, which makes the playbook fail.

We need lsb-release on Debian, so that ansible_lsb
could tell us if this is Debian or Raspbian.

Update certbot (1.6.0 -> 1.7.0)

Update nginx (1.19.1 -> 1.19.2)

Update postgres versions (12.3 -> 12.4, etc)

Undo ill-advised change

In #628 I proposed a CORS change that turns out not to be the root of the issue. Caffeine-addled diagnosis leads to sloppy thinking, and this change should be reverted. In fact, if left it will cause problems for new installations.

Update CORS for ma1sd

Even with the v2 updates listed in #503 and partially addressed in #614, this is still needed to enable identity services to function with Element Desktop/Web. Testing on multiple clients with a clean config has confirmed this, at least for my installation.

Update README.md -> 'many times' -> 'more than once'

Stating "many times" makes me think there is a finite amount of times I can run it before it *will* start causing trouble. But this is not true. So just state it can me ran more than once without causing trouble :)