hiro/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/vale981/matrix-docker-ansible-deploy synced 2025-03-09 12:36:38 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
3988 commits 1 branch 0 tags 9.1 MiB
Commit graph

6 commits

Author SHA1 Message Date
László Várady
5c083b6385 bridge-mautrix-instagram: add option for creating non-federated rooms 2022-03-07 15:00:44 +01:00
László Várady
ba68d2ad36 Remove deprecated community options 
"Community" support

- has been removed from mautrix/facebook in v0.3.3:
  31cac6fb5e

- has been removed from mautrix/signal in v0.2.2:
  1f27a608a6

- will be removed in the next mautrix/instagram release:
  e2ae1ca503

- will be removed in the next mautrix/twitter release:
  3893075265
 2022-03-05 21:57:30 +01: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
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=
 2022-01-04 17:27:25 +02:00
array-in-a-matrix
2d49b95006 missing uppercase in bot name 2021-12-20 16:55:15 -05:00
Marcus Proest
b99372a3c5 initial commit of mautrix-instagram role 2021-02-19 17:20:26 +01:00