3 Commits (eaea2152820badabe3c057db61eb0077c3c9e572)

Author	SHA1	Message	Date
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	85a05f38e8	Allow Synapse worker list to be generated dynamically ... This leads to much easier management and potential safety features (validation). In the future, we could try to avoid port conflicts as well, but it didn't seem worth the effort to do it now. Our port ranges seem large enough. This can also pave the way for a "presets" feature (similar to `matrix_nginx_proxy_ssl_presets`) which makes it even easier for people to configure worker counts.	4 years ago
Slavi Pantaleev	453a4ec2d8	Relocate tasks related to Synapse workers	4 years ago