matrix-docker-ansible-deploy

550 MiB

Albero (Tree): f18555f7f9

Autore	SHA1	Messaggio	Data
Aine	998dafe9c4	Update Honoroit 0.9.11 -> 0.9.12	3 anni fa
Aine	5c36f14b46	Update Honoroit 0.9.10 -> 0.9.11	3 anni fa
Aine	5b0bdced1d	update Honoroit 0.9.9 -> 0.9.10	3 anni fa
Aine	25fd7f0cff	update Honoroit 0.9.8 -> 0.9.9	3 anni fa
Aine	15ce32a30c	update honoroit 0.9.6 -> 0.9.7	3 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
Aine	ffa57055f4	updated honoroit 0.9.4 -> 0.9.5	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
Aine	51b27de1bb	matrix-bot-honoroit: bugfix commands in reply-to mode, add custom prefixes for thread topics	4 anni fa
rakshazi	d7af37e9e9	matrix-bot-honoroit feedback	4 anni fa
rakshazi	407e8c4940	added honoroit	4 anni fa

11 Commit (f18555f7f9eaa0c28362ddb65d3df2437a66c9ba)