Can deploy synapse workers and allow costum amounts of workers for each
type. For documentation on how to use, see `roles/synapse/README.md`.
In a docker deployment, each worker runs in their own docker container
with respective listener configurations. Labels can be declared in
`tasks/configure_workers.yml` for routing of requests.
In systemd deployments, each worker runs in it's own systemd service,
which are marked as being part of the main service, so restarting the
main service will restart all the workers as well.
This module uses synapse's admin API to register users. It requires the
registration shared secret from synapse's config, and allows creating
admin users too.
This module can manage matrix membership in a given room by inviting, kicking or
banning a list specified users.
With the exclusive=True flag, it can be used to ensure that a given list of
members is in a room (and no one else). For this module, users invited into a
room count as members, as they have permissions to join the room.
Co-authored-by: Jan Christian Grünhage <jan.christian@gruenhage.xyz>
During the renaming of Riot to Element, the path for the webapp changed
from /opt/riot to /opt/element. In those folders, the archives are
unpacked, resulting in paths like /opt/element/riot-v${version}. Since
the archives are not yet renamed
(https://github.com/vector-im/element-web/issues/14896), this riot
reference has to stay for now. In the renaming, this was accidentally
changed prematurely, resulting in this regression.
Riot is now Element, and therefore this role has to do a lot of
`s/riot/element/g`. There's still a few references to riot here and
there, but fixing those depends on external changes.
This does not attempt any automatic migration, you will need to clean
up the old webroot or container yourself.
BREAKING CHANGE: role name and variable names have changed
