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

47 lines
1.6 KiB
YAML
Raw Normal View History

moved role out of matrix-ansible
2018-07-30 14:56:33 +00:00
---
support deployment through docker instead of directly onto the host
2019-02-16 10:25:57 +00:00
- name: check that sypervision and deployment are compatible
fail:
msg: "Either both or neither of deployment and supervision method should be docker."
Make the linter happy
2019-02-17 23:47:45 +00:00
when: (matrix_synapse_supervision_method == "docker" and matrix_synapse_deployment_method != "docker") or
(matrix_synapse_deployment_method == "docker" and matrix_synapse_supervision_method != "docker")
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
tags: ['deploy', 'deploy-synapse']
Make the ansible linter happy remove trailing whitespaces
2019-02-17 23:27:45 +00:00
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
- name: Fail if workers are enabled but no redis is configured for synapse
fail:
msg: "Redis needs to be enabled on synapse in order for workers to be able to be run"
when: matrix_synapse_workers_enabled|bool and not matrix_synapse_redis_enabled|bool
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
tags: ['deploy', 'deploy-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
- name: prepare user, group and base directory
import_tasks: prepare.yml
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
tags: ['prepare', 'prepare-synapse',
'deploy', 'deploy-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
- name: configure workers
import_tasks: configure_workers.yml
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
tags: ['deploy', 'deploy-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
when: matrix_synapse_workers_enabled
- name: configure config overrides from workers
import_tasks: configure_worker_overrides.yml
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
tags: ['deploy', 'deploy-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
when: matrix_synapse_workers_enabled
moved role out of matrix-ansible
2018-07-30 14:56:33 +00:00
- name: configure synapse
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
include_tasks: configure.yml
tags: ['always']
moved role out of matrix-ansible
2018-07-30 14:56:33 +00:00
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
- name: deploy workers
import_tasks: deploy_workers.yml
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
tags: ['deploy', 'deploy-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
when: matrix_synapse_workers_enabled
support deployment through docker instead of directly onto the host
2019-02-16 10:25:57 +00:00
- name: deploy synapse
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
include_tasks: deployment.yml
tags: ['always']
support deployment through docker instead of directly onto the host
2019-02-16 10:25:57 +00:00
moved role out of matrix-ansible
2018-07-30 14:56:33 +00:00
- name: configure service
import_tasks: systemd.yml
feat(synapse): support partial execution with `prepare` and `deploy` tags
2021-05-10 10:27:11 +00:00
tags: ['deploy', 'deploy-synapse']
support deployment through docker instead of directly onto the host
2019-02-16 10:25:57 +00:00
when: matrix_synapse_supervision_method == "systemd"
Reference in a new issue Copy permalink