matrix-docker-ansible-deploy

281 MiB

Struktur: 3684842e86

Autor	SHA1	Nachricht	Datum
Suguru Hirahara	afd122330b	Add license information to files for matrix-client-hydrogen This commit adds copyright attributions in SPDX to the files for matrix-client-hydrogen following 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	2511b34a7c	Stop containers gracefully, instead of outright killing them	vor 2 Jahren
Slavi Pantaleev	6a52be7987	Add (native) Traefik support to matrix-client-hydrogen Previously, it had to go through matrix-nginx-proxy. It's exposed to Traefik directly via container labels now Serving at a path other than `/` doesn't work well yet.	vor 3 Jahren
Slavi Pantaleev	64e2b26ed5	Fix Hydrogen failing to start We were mounting our own configuration to `/usr/share/nginx/html/config.json`, which is a symlink to `/tmp/config.json`. So we effectively mount our file to `/tmp/config.json`. When starting: - if Hydrogen sees a `CONFIG_OVERRIDE` environment variable, it will try to save it into our read-only config file and fail. - if Hydrogen doesn't see a `CONFIG_OVERRIDE` environment variable (the path we go through, because we don't pass such a variable), it will try to copy its bundled configuration (`/config.json.bundled`) to `/tmp/config.json`. Because our configuration is mounted as read-only, it will fail. In both cases, it will fail with: > cp: can't create '/tmp/config.json': File exists Source: `3720de36bb/docker/dynamic-config.sh` We work around this by mounting our configuration on top of the bundled one (`/config.json.bundled`). We then let Hydrogen's startup script copy it to `/tmp/config.json` (a tmpfs we've mounted into the container) and use it from there.	vor 3 Jahren
Matthew Cengia	3453fff901	Use upstream Docker image for amd64 rather than self-build	vor 3 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

10 Commits (3684842e86adc0b027e6960ff95f9500a3b8f32d)