matrix-docker-ansible-deploy

251 MiB

Struktur: 2921900a79

Autor	SHA1	Nachricht	Datum
Slavi Pantaleev	51ab9ed9ff	Adjust `lstrip_blocks` to use a `bool` value for compatibility with ansible-core>=2.19.0 Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/4445	vor 9 Monaten
Suguru Hirahara	807da74334	Add license information to files for MX bridges As the future for the MX bridges in this playbook and by themselves seems uncertain, this commit adds license information in SPDX format to the files for those bridges, before the bridges would be deprecated and possibly get removed from the project. Please note that .license files are added for the files which would be broken if such information are added as header, following the REUSE's specification. Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	vor 1 Jahr
Slavi Pantaleev	d12643eb91	Do not use `docker stop --time` (deprecated in Docker v28 in favor of `--timeout` or just `-t`) `-t` works on both old and new Docker versions, so it's best to use that.	vor 1 Jahr
Slavi Pantaleev	c0308307e2	Make homeserver services sleep after startup, instead of all dependencies sleeping separately This is an attempt at optimizing service startup. The effect is most pronounced when many services are restarted one by one. The systemd service manager role sometimes does this - for example when `just install-service synapse` runs. In such cases, a 5-second delay for each Synapse worker service (or other bridge/bot service that waits on the homeserver) quickly adds up to a lot. When services are all stopped fully and then started, the effect is not so pronounced, because `matrix-synapse.service` starts first and pulls all worker services (defined as `Wants=` for it). Later on, when the systemd service manager role "starts" these worker services, they're started already. Even if they had a 5-second wait each, it would have happened in parallel.	vor 2 Jahren
Slavi Pantaleev	1e19fee772	Move matrix-bridge-mx-puppet-steam to its own container network	vor 2 Jahren
Slavi Pantaleev	2511b34a7c	Stop containers gracefully, instead of outright killing them	vor 2 Jahren
Slavi Pantaleev	7086c0ebe3	matrix_host_command_sh -> devture_systemd_docker_base_host_command_sh (via com.devture.ansible.role.systemd_docker_base)	vor 3 Jahren
Slavi Pantaleev	a9a81460ec	matrix_host_command_docker -> devture_systemd_docker_base_host_command_docker (via com.devture.ansible.role.systemd_docker_base)	vor 3 Jahren
Slavi Pantaleev	f03f716989	matrix_systemd_unit_home_path -> devture_systemd_docker_base_systemd_unit_home_path (via com.devture.ansible.role.systemd_docker_base)	vor 3 Jahren
Slavi Pantaleev	410a915a8a	Move roles/matrix* to roles/custom/matrix* This paves the way for installing other roles into `roles/galaxy` using `ansible-galaxy`, similar to how it's done in: - https://github.com/spantaleev/gitea-docker-ansible-deploy - https://github.com/spantaleev/nextcloud-docker-ansible-deploy In the near future, we'll be removing a lot of the shared role code from here and using upstream roles for it. Some of the core `matrix-*` roles have already been extracted out into other reusable roles: - https://github.com/devture/com.devture.ansible.role.postgres - https://github.com/devture/com.devture.ansible.role.systemd_docker_base - https://github.com/devture/com.devture.ansible.role.timesync - https://github.com/devture/com.devture.ansible.role.vars_preserver - https://github.com/devture/com.devture.ansible.role.playbook_runtime_messages - https://github.com/devture/com.devture.ansible.role.playbook_help We just need to migrate to those.	vor 3 Jahren

11 Commits (2921900a790e907efdb5cf7e1e6492dc1ff0b866)