matrix-docker-ansible-deploy

Commit grafiek

Auteur	SHA1	Bericht	Datum
Suguru Hirahara	c385bee7af	Re-run "reuse annotate" to sort statements Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	1 jaar geleden
Suguru Hirahara	dc9672a86f	Tribute to deprecated components: add license information to files for matrix-bridge-appservice-webhooks This commit adds copyright headers to Markdown, YAML, and labels.j2 files. For the rest of the files, which are ones in YAML and JSON files with the extention ".j2", ".license" files are added following the REUSE's specification. Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	1 jaar geleden
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.	1 jaar geleden
Slavi Pantaleev	e782e91fbd	Fix some variable typos in matrix-appservice-webhooks.service	2 jaren geleden
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.	2 jaren geleden
Slavi Pantaleev	a5618a893b	Move matrix-bridge-appservice-webhooks to its own container network	2 jaren geleden
Slavi Pantaleev	2511b34a7c	Stop containers gracefully, instead of outright killing them	2 jaren geleden
Slavi Pantaleev	7086c0ebe3	matrix_host_command_sh -> devture_systemd_docker_base_host_command_sh (via com.devture.ansible.role.systemd_docker_base)	3 jaren geleden
Slavi Pantaleev	a9a81460ec	matrix_host_command_docker -> devture_systemd_docker_base_host_command_docker (via com.devture.ansible.role.systemd_docker_base)	3 jaren geleden
Slavi Pantaleev	f03f716989	matrix_systemd_unit_home_path -> devture_systemd_docker_base_systemd_unit_home_path (via com.devture.ansible.role.systemd_docker_base)	3 jaren geleden
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.	3 jaren geleden

11 Commits (ae58880f0cdfaa006d5c7d3753f2d7c19bbbec1d)