1
0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-12-12 08:43:55 +02:00
Commit Graph

11 Commits

Author SHA1 Message Date
Aine
998dafe9c4
Update Honoroit 0.9.11 -> 0.9.12 2022-08-04 22:02:45 +03:00
Aine
5c36f14b46
Update Honoroit 0.9.10 -> 0.9.11 2022-07-30 13:24:59 +03:00
Aine
5b0bdced1d
update Honoroit 0.9.9 -> 0.9.10 2022-07-18 21:24:17 +03:00
Aine
25fd7f0cff
update Honoroit 0.9.8 -> 0.9.9 2022-05-31 20:32:10 +03:00
Aine
15ce32a30c
update honoroit 0.9.6 -> 0.9.7 2022-04-18 19:37:14 +03:00
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".
2022-04-11 09:05:33 +03:00
Aine
ffa57055f4
updated honoroit 0.9.4 -> 0.9.5 2022-02-24 20:50:06 +02:00
Slavi Pantaleev
86c36523df Replace ExecStopPost with ExecStop
Reverts b1b4ba501f, 90c9801c56, a3c84f78ca, ..

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.
2022-02-05 12:13:36 +02:00
Aine
51b27de1bb
matrix-bot-honoroit: bugfix commands in reply-to mode, add custom prefixes for thread topics 2022-01-19 18:33:51 +02:00
rakshazi
d7af37e9e9
matrix-bot-honoroit feedback 2022-01-07 09:41:52 +02:00
rakshazi
407e8c4940
added honoroit 2022-01-06 20:30:10 +02:00