matrix-docker-ansible-deploy/roles/matrix-synapse/templates/synapse/worker.yaml.j2

#jinja2: lstrip_blocks: "True"
worker_app: synapse.app.{{ item.type }}
worker_name: {{ item.type ~ ':' ~ item.port }}

worker_replication_host: 127.0.0.1
worker_replication_http_port: {{ matrix_synapse_replication_http_port }}

{% if item.type not in [ 'appservice', 'federation_sender', 'pusher' ] %}
worker_listeners:
  - type: http
    port: {{ item.port }}
    resources:
      - names:
{% if item.type in [ 'generic_worker', 'frontend_proxy', 'user_dir' ] %}
        - client
{% endif %}
{% if item.type in [ 'generic_worker' ] %}
        - federation
{% elif item.type in [ 'media_repository' ] %}
        - media
{% endif %}
{% endif %}

  - type: metrics
    bind_address: ''
    port: {{ item.metrics_port }}

{% if item.type == 'frontend_proxy' %}
worker_main_http_uri: http://127.0.0.1:8008
{% endif %}

worker_daemonize: false
worker_log_config: /data/{{ matrix_server_fqn_matrix }}.log.config
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago			`#jinja2: lstrip_blocks: "True"`
synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD) 4 years ago			`worker_app: synapse.app.{{ item.type }}`
			`worker_name: {{ item.type ~ ':' ~ item.port }}`
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago
			`worker_replication_host: 127.0.0.1`
			`worker_replication_http_port: {{ matrix_synapse_replication_http_port }}`

synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD) 4 years ago			`{% if item.type not in [ 'appservice', 'federation_sender', 'pusher' ] %}`
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago			`worker_listeners:`
			`- type: http`
			`port: {{ item.port }}`
			`resources:`
			`- names:`
synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD) 4 years ago			`{% if item.type in [ 'generic_worker', 'frontend_proxy', 'user_dir' ] %}`
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago			`- client`
Add worker_name to synapse worker config template & restrict federation listener; frontend_proxy / user_dir don't need it 4 years ago			`{% endif %}`
synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD) 4 years ago			`{% if item.type in [ 'generic_worker' ] %}`
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago			`- federation`
synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD) 4 years ago			`{% elif item.type in [ 'media_repository' ] %}`
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago			`- media`
			`{% endif %}`
			`{% endif %}`

synapse workers: define and expose METRICS port for each worker As seen on TV: https://github.com/matrix-org/synapse/blob/master/docs/metrics-howto.md#monitoring-workers 4 years ago			`- type: metrics`
			`bind_address: ''`
			`port: {{ item.metrics_port }}`

synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD) 4 years ago			`{% if item.type == 'frontend_proxy' %}`
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago			`worker_main_http_uri: http://127.0.0.1:8008`
			`{% endif %}`
refactor to use new workers and routes they serve 4 years ago
Add initial support for synapse workers · needs documentation; no checks yet for port clashes or typos in worker name · according to https://github.com/matrix-org/synapse/wiki/Workers-setup-with-nginx#results about 90% of requests go to the synchrotron endpoint · thus, the synchrotron worker is especially suited to be load-balanced · most of the other workers are documented to support only a single instance · https://github.com/matrix-org/synapse/blob/master/docs/workers.md 5 years ago			`worker_daemonize: false`
			`worker_log_config: /data/{{ matrix_server_fqn_matrix }}.log.config`