matrix-docker-ansible-deploy

Graphique des révisions

Auteur	SHA1	Message	Date
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	il y a 8 mois
Suguru Hirahara	9ac31fb37c	Add license information to matrix-bridge-appservice-irc Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	il y a 1 an
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.	il y a 1 an
Suguru Hirahara	bad06d01c2	Update files for matrix-appservice-irc: adopt the common description for logging verbosity Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	il y a 1 an
Suguru Hirahara	684f1dc16e	Update files for matrix-appservice-irc: add the common section "Troubleshooting" Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	il y a 1 an
Suguru Hirahara	55fcaac1f1	Fix capitalization: matrix → Matrix Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	il y a 1 an
Suguru Hirahara	3fb2752714	Replace (your.)server.name with example.com Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	il y a 1 an
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.	il y a 2 ans
Slavi Pantaleev	dcdc43b6aa	Move matrix-bridge-appservice-irc to its own container network	il y a 2 ans
Slavi Pantaleev	2511b34a7c	Stop containers gracefully, instead of outright killing them	il y a 2 ans
Slavi Pantaleev	7086c0ebe3	matrix_host_command_sh -> devture_systemd_docker_base_host_command_sh (via com.devture.ansible.role.systemd_docker_base)	il y a 3 ans
Slavi Pantaleev	a9a81460ec	matrix_host_command_docker -> devture_systemd_docker_base_host_command_docker (via com.devture.ansible.role.systemd_docker_base)	il y a 3 ans
Slavi Pantaleev	f03f716989	matrix_systemd_unit_home_path -> devture_systemd_docker_base_systemd_unit_home_path (via com.devture.ansible.role.systemd_docker_base)	il y a 3 ans
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.	il y a 3 ans

14 Révisions (fdbee0428ca752d2e5b1792fbb0f5b59ab440cd3)