Mirrors/ansible-collection-famedly-matrix
2
0
Fork 0
mirror of https://github.com/famedly/ansible-collection-matrix synced 2024-12-14 13:12:27 +00:00
Code Issues Projects Releases Packages Wiki Activity
ansible-collection-famedly-.../roles/synapse/defaults/main.yml

83 lines
3.3 KiB
YAML
Raw Normal View History

moved role out of matrix-ansible
2018-07-30 14:56:33 +00:00
---
Adjust variable definitions
2019-02-14 23:24:21 +00:00
matrix_synapse_extra_config: {}
support deployment through docker instead of directly onto the host
2019-02-16 10:25:57 +00:00
matrix_synapse_deployment_method: pip
matrix_synapse_supervision_method: systemd
Add default value for base path and secrets directory
2019-02-21 00:28:43 +00:00
matrix_synapse_base_path: "/opt/synapse"
matrix_synapse_secrets_path: "{{ matrix_synapse_base_path }}/secrets"
Use the configurable matrix in the defaults
2019-02-21 22:15:38 +00:00
matrix_synapse_dh_path: "{{ matrix_synapse_base_path }}/tls/{{ matrix_server_name }}.dh"
feat(synapse): allow public_baseurl configuration
2021-02-08 05:20:48 +00:00
matrix_synapse_public_baseurl: "https://{{ matrix_server_name }}"
Use the configurable matrix in the defaults
2019-02-21 22:15:38 +00:00
matrix_synapse_signing_key_path: "{{ matrix_synapse_base_path }}/tls/{{ matrix_server_name }}.signing.key"
feat(synapse): support deploying release candidates
2020-10-09 15:20:46 +00:00
matrix_synapse_version: "{{ matrix_synapse_unstable | ternary(matrix_synapse_unstable_version, matrix_synapse_stable_version) }}"
matrix_synapse_unstable: false
update(synapse): bump stable version to 1.69.0
2022-10-20 17:48:38 +00:00
matrix_synapse_stable_version: "1.69.0"
matrix_synapse_unstable_version: "1.69.0"
make log dir configurable
2019-03-24 15:51:22 +00:00
matrix_synapse_log_dir: "/var/log/matrix_synapse"
Reduce log retention period to 14 days
2020-01-10 00:00:38 +00:00
matrix_synapse_log_days_keep: 14
Use the configurable matrix in the defaults
2019-02-21 22:15:38 +00:00
matrix_synapse_pid_file: "{{ matrix_synapse_base_path }}/synapse.pid"
feat(synapse): allow overriding docker_networks and etc_hosts
2021-01-04 15:14:16 +00:00
matrix_synapse_docker_networks: []
matrix_synapse_docker_etc_hosts: {}
support deployment through docker instead of directly onto the host
2019-02-16 10:25:57 +00:00
matrix_synapse_docker_ports: ["8008:8008", "8448:8448"]
matrix_synapse_docker_labels: {}
fix(synapse): allow specifying env vars for the docker container
2021-03-25 11:52:53 +00:00
matrix_synapse_docker_env: {}
feat(synapse)!: allow overriding recreate and disable by default
2021-02-01 15:25:08 +00:00
matrix_synapse_docker_recreate: false
feat(synapse): support docker command, entrypoint and pull configurations
2021-02-22 06:21:28 +00:00
matrix_synapse_docker_pull: true
allow more mounts for docker container
2019-12-09 13:47:21 +00:00
matrix_synapse_extra_docker_volumes: []
feat(synapse): support docker command, entrypoint and pull configurations
2021-02-22 06:21:28 +00:00
matrix_synapse_docker_entrypoint: "python"
matrix_synapse_docker_command:
- "-m"
- "synapse.app.homeserver"
- "-c"
- "{{ matrix_synapse_base_path }}/homeserver.yaml"
move container ref to variable
2019-11-12 12:30:07 +00:00
matrix_synapse_container_ref: "docker.io/matrixdotorg/synapse"
chore(synapse): remove v from container version label
2020-09-19 09:44:30 +00:00
matrix_synapse_container_tag: "v{{ matrix_synapse_version }}"
pull out container name into a variable
2020-05-27 16:35:20 +00:00
matrix_synapse_container_name: "synapse"
feat(synapse): add support for deploying workers Can deploy synapse workers and allow costum amounts of workers for each type. For documentation on how to use, see `roles/synapse/README.md`. In a docker deployment, each worker runs in their own docker container with respective listener configurations. Labels can be declared in `tasks/configure_workers.yml` for routing of requests. In systemd deployments, each worker runs in it's own systemd service, which are marked as being part of the main service, so restarting the main service will restart all the workers as well.
2020-10-02 07:49:51 +00:00
# Redis config
matrix_synapse_redis_enabled: false
matrix_synapse_redis_host: ~
matrix_synapse_redis_port: 6379
matrix_synapse_redis_pass: ~
feat(synapse): provide variable for controlling metrics
2021-09-10 08:19:57 +00:00
# Monitoring
matrix_synapse_metrics_enabled: false
matrix_synapse_worker_metrics_enabled: "{{ matrix_synapse_metrics_enabled | bool }}"
matrix_synapse_worker_metrics_port: 9101
feat(synapse): add support for deploying workers Can deploy synapse workers and allow costum amounts of workers for each type. For documentation on how to use, see `roles/synapse/README.md`. In a docker deployment, each worker runs in their own docker container with respective listener configurations. Labels can be declared in `tasks/configure_workers.yml` for routing of requests. In systemd deployments, each worker runs in it's own systemd service, which are marked as being part of the main service, so restarting the main service will restart all the workers as well.
2020-10-02 07:49:51 +00:00
# Worker control config
matrix_synapse_workers_enabled: false
matrix_synapse_worker_replication_host: "{{ matrix_synapse_container_name }}"
matrix_synapse_worker_replication_port: 9003
matrix_synapse_worker_replication_bind_ip: "127.0.0.1"
matrix_synapse_worker_listener_base_port: 16000
matrix_synapse_worker_listener_bind_base_ip: "0.0.0.0"
matrix_synapse_worker_labels: {}
matrix_synapse_worker_image: "{{ matrix_synapse_container_ref }}:{{ matrix_synapse_container_tag }}"
# Control which workers (or how many) to run
matrix_synapse_workers_client: 0
matrix_synapse_workers_federation_in: 0
matrix_synapse_workers_federation_out: 0
matrix_synapse_workers_media: 0
matrix_synapse_worker_push: false
matrix_synapse_worker_appservice: false
matrix_synapse_worker_user_search: false
# Control where which paths get routed
matrix_synapse_worker_client_endpoints: >-
{{
matrix_synapse_worker_client_sync_endpoints
+ matrix_synapse_worker_client_api_endpoints
chore(synapse): update routing to worker endpoints
2022-04-22 09:42:47 +00:00
+ matrix_synapse_worker_client_encryption_endpoints
feat(synapse): add support for deploying workers Can deploy synapse workers and allow costum amounts of workers for each type. For documentation on how to use, see `roles/synapse/README.md`. In a docker deployment, each worker runs in their own docker container with respective listener configurations. Labels can be declared in `tasks/configure_workers.yml` for routing of requests. In systemd deployments, each worker runs in it's own systemd service, which are marked as being part of the main service, so restarting the main service will restart all the workers as well.
2020-10-02 07:49:51 +00:00
+ matrix_synapse_worker_client_login_endpoints
chore(synapse): update routing to worker endpoints
2022-04-22 09:42:47 +00:00
+ matrix_synapse_worker_client_send_endpoints
+ matrix_synapse_worker_client_device_endpoints
+ matrix_synapse_worker_client_account_data_endpoints
+ matrix_synapse_worker_client_receipts_endpoints
+ matrix_synapse_worker_client_presence_endpoints
feat(synapse): add support for deploying workers Can deploy synapse workers and allow costum amounts of workers for each type. For documentation on how to use, see `roles/synapse/README.md`. In a docker deployment, each worker runs in their own docker container with respective listener configurations. Labels can be declared in `tasks/configure_workers.yml` for routing of requests. In systemd deployments, each worker runs in it's own systemd service, which are marked as being part of the main service, so restarting the main service will restart all the workers as well.
2020-10-02 07:49:51 +00:00
}}
feat(synapse): add option to refresh container certificates
2021-09-22 10:08:03 +00:00
# Certificate management
matrix_synapse_container_certificate_refresh: false
matrix_synapse_container_certificate_refresh_command: "update-ca-certificates --fresh"
matrix_synapse_container_certificate_refresh_user_id: 0
Reference in a new issue Copy permalink