Add sample worker files for pusher and federation_sender

[dklimpel]

Related to:

• Expand and improve workers documentation and example configuration #9072
• Include a sample worker config for a Big deployment #8557

Pull Request Checklist

• Pull request is based on the develop branch
• Pull request includes a changelog file. The entry should:
  • Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from EventStore to EventWorkerStore.".
  • Use markdown where necessary, mostly for code blocks.
  • End with either a period (.) or an exclamation mark (!).
  • Start with a capital letter.
  • Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry.
• Pull request includes a sign off
• Code style is correct
  (run the linters)

Signed-off-by: Dirk Klimpel [email protected]

[dklimpel]

In my environment, this configuration is running.

In #12737 was added a config with an undocumented replication listener.

synapse/contrib/docker_compose_workers/workers/synapse-federation-sender-1.yaml

Lines 1 to 12 in 7b7478e

	worker_app: synapse.app.federation_sender
	worker_name: synapse-federation-sender-1
	# The replication listener on the main synapse process.
	worker_replication_host: synapse
	worker_replication_http_port: 9093
	worker_listeners:
	- type: http
	port: 8034
	resources:
	- names: [replication]

[squahtx]

I think the replication listener in #12737 is unnecessary. The list of federation senders is stored in WorkerConfig.federation_shard_config, and nothing seems to send out replication requests based off of it.

[squahtx]

lgtm! Thanks for updating the docs.

[squahtx]

I think the replication listener in #12737 is unnecessary. The list of federation senders is stored in WorkerConfig.federation_shard_config, and nothing seems to send out replication requests based off of it.