Also get rid of `--tags=update-user-password` in the
`matrix-dendrite` role, as what we had doesn't work.
We may be able to do it with some Ansible helper or something else.
For now, we'll omit this feature.
All the `matrix_s3_*` stuff happens in the `matrix-synapse` role.
If we are to have such S3 support for Dendrite, we should probably
extract it out of the `matrix-synapse` role (into a `matrix-s3` role or
`matrix-goofys`, etc.) and wire `matrix-dendrite` accordingly.
This may or may not be done in the future though. For now, I'm
cleaning things up in the `matrix-dendrite` role.
Seems like Dendrite encourages serving both the Client and Federation
API at the same port.
Coming from Synapse and how things are done there, we have separate
ports. Using separate ports probably makes matrix-corporal (etc.)
integration easier, so separating the APIs by default probably makes
sense.
The goal is to have a single variable which tells us which homeserver
software is in use. Much simpler than having if/elif/elif checks for
variables like (`matrix_synapse_enabled` and `matrix_dendrite_enabled`, etc.)
everywhere.
* Upgrade Mjolnir from 1.1.20 to version 1.2.1
https://hub.docker.com/r/matrixdotorg/mjolnir/tags
using the "latest" tag seems inefficient as it doesn't actually redirect to the latest release
In any case, the latest release is now 1.2.1
docker pull matrixdotorg/mjolnir:v1.2.1
* Fixup
Co-authored-by: Slavi Pantaleev <slavi@devture.com>
The check was checking for an empty string in `matrix_jitsi_prosody_auth_internal_accounts`,
which is unlikely to happen. We should check for an empty list instead.
The check was not validating username/password values, so telling the user that they need a non-empty
username/password is misleading. It was merely checking if there's at least one entry in the list.
This patch adjusts the check and message accordingly.