matrix-docker-ansible-deploy

Graf revizí

Autor	SHA1	Zpráva	Datum
Suguru Hirahara	7d210cbafd	Add license information to files for matrix-bot-mjolnir Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>	před 1 rokem
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.	před 1 rokem
Catalan Lover	c4992ca018	Explicitly Declare Draupnir and Mjolnir Config and enter Bot Mode This should resolve [#2296](https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2296) by fixing the noted issue. This also paves the way for in the future working on D4A mode but that would require a rework to how these variables are done.	před 2 roky
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.	před 2 roky
Slavi Pantaleev	867af6385a	Move matrix-bot-mjolnir to its own container network	před 2 roky
Slavi Pantaleev	2511b34a7c	Stop containers gracefully, instead of outright killing them	před 2 roky
Slavi Pantaleev	593b3157b9	Fix systemd service Wants for mjolnir and draupnir Patch contributed by JulianF.	před 2 roky
Slavi Pantaleev	7086c0ebe3	matrix_host_command_sh -> devture_systemd_docker_base_host_command_sh (via com.devture.ansible.role.systemd_docker_base)	před 3 roky
Slavi Pantaleev	a9a81460ec	matrix_host_command_docker -> devture_systemd_docker_base_host_command_docker (via com.devture.ansible.role.systemd_docker_base)	před 3 roky
Slavi Pantaleev	f03f716989	matrix_systemd_unit_home_path -> devture_systemd_docker_base_systemd_unit_home_path (via com.devture.ansible.role.systemd_docker_base)	před 3 roky
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.	před 3 roky

11 Revize (98e4f369b7e5bd4eae76fdba2d191ffe2ff4b849)