8 Commits (3a3a0b5c9a6039706c488ac439c9a27777cb035e)

Author	SHA1	Message	Date
Slavi Pantaleev	5f3f460cda	Restore support for appservice and user_dir workers	2 years ago
Slavi Pantaleev	226c550ffa	Add support for stream writer Synapse workers ... As stream writer workers are also powered by the `generic_worker` Synapse app, this necessitated that we provide means for distinguishing between them and regular `generic_workers`. I've also taken the time to optimize nginx configuration generation (more Jinja2 macro usage, less duplication). Worker names have also changed. Workers are now named sequentially like this: - `matrix-synapse-worker-0-generic` - `matrix-synapse-worker-1-stream-writer-typing` - `matrix-synapse-worker-2-pusher` instead of `matrix-synapse-worker_generic_worker-18111` (indexed with a port number). People who modify `matrix_synapse_workers_enabled_list` directly will need to adjust their configuration.	2 years ago
Slavi Pantaleev	983bf819ef	Explictly set Synapse's worker configuration's owner/permissions	2 years ago
Slavi Pantaleev	ddf18eadc7	More ansible-lint fixes	2 years ago
Slavi Pantaleev	34cdaade08	Use fully-qualified module names for builtin Ansible modules ... Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939	2 years ago
Marko Weltzer	7e5b88c3b7	fix: all praise the allmighty yamllinter	3 years ago
Slavi Pantaleev	d6c4d41c2b	Define instanceId property on workers ... This give us the possibility to run multiple instances of workers that that don't expose a port. Right now, we don't support that, but in the future we could run multiple `federation_sender` or `pusher` workers, without them fighting over naming (previously, they'd all be named something like `matrix-synapse-worker-pusher-0`, because they'd all define `port` as `0`).	4 years ago
Slavi Pantaleev	453a4ec2d8	Relocate tasks related to Synapse workers	4 years ago