matrix-docker-ansible-deploy

554 MiB

Albero (Tree): e119512c59

Autore	SHA1	Messaggio	Data
ThellraAK	1c8f21c738	Adding logging configuration and default to the rest of the mautrixes that don't have them	3 anni fa
Aine	44f2234c99	define matrix_admin in matrix-base	4 anni fa
Aine	55d8e3dfdd	mautrix-based bridges: add matrix_admin	4 anni fa
Aine	2689a0981a	mautrix-based bridges - set log level = warn(ing)	4 anni fa
Slavi Pantaleev	0364c6c634	Suppress old container cleanup (kill/rm) failures People often report and ask about these "failures". More-so previously, when the `docker kill/rm` output was collected, but it still happens now when people do `systemctl status matrix-something` and notice that it says "FAILURE". Suppressing to avoid further time being wasted on saying "this is expected".	4 anni fa
László Várady	d6df1e7135	bridge-mautrix-googlechat: add option for creating non-federated rooms	4 anni fa
Slavi Pantaleev	86c36523df	Replace ExecStopPost with ExecStop Reverts b1b4ba501fdfaa, 90c9801c560b6, a3c84f78ca9c65a, .. I haven't really traced it (yet), but on some servers, I'm observing `ansible-playbook ... --tags=start` completing very slowly, waiting to stop services. I can't reproduce this on all Matrix servers I manage. I suspect that either the systemd version is to blame or that some specific service is not responding well to some `docker kill/rm` command. `ExecStop` seems to work great in all cases and it's what we've been using for a very long time, so I'm reverting to that.	4 anni fa
Slavi Pantaleev	b1b4ba501f	Replace ExecStop with ExecStopPost ExecStopPost should allow us to clean up (docker kill + docker rm) even if the ExecStart (docker run ..) command failed, and not just after a graceful service stop was initiated. Source: https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStopPost=	4 anni fa
Luke	1dac525e63	Added Mautrix Google Chat	4 anni fa

9 Commit (e119512c5928ded244ef629fbf8ef37f7694c4b3)