mirror/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-11-10 20:57:41 +01:00
Code Issues Packages Projects Releases Wiki Activity
f201bca519
matrix-docker-ansible-deploy/roles/matrix-synapse/templates/synapse/worker.yaml.j2

34 lines
906 B
Plaintext
Raw Normal View History

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
2020-04-10 23:44:53 +02:00
#jinja2: lstrip_blocks: "True"
synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD)
2020-10-28 07:13:19 +01:00
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
2020-04-10 23:44:53 +02:00
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)
2020-10-28 07:13:19 +01:00
{% 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
2020-04-10 23:44:53 +02:00
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)
2020-10-28 07:13:19 +01:00
{% 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
2020-04-10 23:44:53 +02:00
- client
Add worker_name to synapse worker config template & restrict federation listener; frontend_proxy / user_dir don't need it
2020-09-09 19:57:49 +02:00
{% endif %}
synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD)
2020-10-28 07:13:19 +01:00
{% 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
2020-04-10 23:44:53 +02:00
- federation
synapse workers: reworkings + get endpoints from upstream docs via awk (yes, a bit awkward and brittle… xD)
2020-10-28 07:13:19 +01:00
{% 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
2020-04-10 23:44:53 +02:00
- 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
2020-12-01 22:49:15 +01:00
- 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)
2020-10-28 07:13:19 +01:00
{% 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
2020-04-10 23:44:53 +02:00
worker_main_http_uri: http://127.0.0.1:8008
{% endif %}
refactor to use new workers and routes they serve
2020-08-28 13:53:39 +02:00
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
2020-04-10 23:44:53 +02:00
worker_daemonize: false
worker_log_config: /data/{{ matrix_server_fqn_matrix }}.log.config
Reference in New Issue Copy Permalink