matrix-docker-ansible-deploy

916 MiB

Aborescence: 3bbed3a011

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	aae64ebde4	Add license information to files for matrix-synapse-reverse-proxy-companion 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
Michael Hollister	bd027159b1	Added extra systemd service arguments to synapse workers and proxy companion	il y a 2 ans
Slavi Pantaleev	bbd9493b8f	Handle /_matrix Client-Server and Federation APIs directly at matrix-synapse-reverse-proxy-companion	il y a 2 ans
Slavi Pantaleev	2511b34a7c	Stop containers gracefully, instead of outright killing them	il y a 2 ans
Slavi Pantaleev	e018663ba4	Attach ma1sd/nginx-proxy/synapse-reverse-proxy-companion to additional networks in a better way Switching from doing "post-start" loop hacks to running the container in 3 steps: `create` + potentially connect to additional networks + `start`. This way, the container would be connected to all its networks even at the very beginning of its life.	il y a 3 ans
Slavi Pantaleev	42f3c3cbf6	Improve command for connecting to additional container networks	il y a 3 ans
Slavi Pantaleev	e9e84341a9	Reverse-proxy to Synapse via matrix-synapse-reverse-proxy-companion Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2090	il y a 3 ans

9 Révisions (3bbed3a011f19e98bd47fb36457d2da59c6db07e)