Suguru Hirahara
766ad9ebaa
Add license information to matrix-bridge-appservice-discord
...
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org >
2025-02-28 14:46:49 +09:00
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.
2025-02-22 21:42:18 +02:00
Suguru Hirahara
811abc09a8
Update files for matrix-appservice-discord: sort the logging levels
...
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org >
2025-02-01 02:41:23 +09:00
Suguru Hirahara
ae864830e0
Update the URL to matrix-appservice-discord
...
The URL seems to have been changed at least since several years though the exact date is unknown to me, considering the latest tagged docker image on https://hub.docker.com/r/halfshot/matrix-appservice-discord/tags (https://hub.docker.com/layers/halfshot/matrix-appservice-discord/develop/images/sha256-a1015907545603448d2d8e2ea0d31f0fdb6c7676009e2cb38e324440a9284317 ) is dated Feb 15, 2021.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org >
2024-10-28 17:18:03 +09:00
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.
2024-01-12 12:45:18 +02:00
Slavi Pantaleev
7d625011a1
Move matrix-bridge-appservice-discord to its own container network
2024-01-07 10:23:01 +02:00
Slavi Pantaleev
2511b34a7c
Stop containers gracefully, instead of outright killing them
2023-12-06 11:52:23 +02:00
Slavi Pantaleev
7086c0ebe3
matrix_host_command_sh -> devture_systemd_docker_base_host_command_sh (via com.devture.ansible.role.systemd_docker_base)
2022-11-04 16:40:25 +02:00
Slavi Pantaleev
a9a81460ec
matrix_host_command_docker -> devture_systemd_docker_base_host_command_docker (via com.devture.ansible.role.systemd_docker_base)
2022-11-04 16:39:35 +02:00
Slavi Pantaleev
f03f716989
matrix_systemd_unit_home_path -> devture_systemd_docker_base_systemd_unit_home_path (via com.devture.ansible.role.systemd_docker_base)
2022-11-04 16:37:47 +02:00
Slavi Pantaleev
4cbea602dd
Sync appservice-discord configuration with upstream
2022-11-03 11:50:40 +02:00
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.
2022-11-03 09:11:29 +02:00
