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

26 Commits

Author SHA1 Message Date
Marko Weltzer
819574b8ba
Merge branch 'spantaleev:master' into master 2022-02-05 21:37:53 +01:00
Marko Weltzer
7e5b88c3b7 fix: all praise the allmighty yamllinter 2022-02-05 21:32:54 +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
GoliathLabs
b4ecadcb2f
Updated: Heisenbridge to 1.10.1 2022-02-05 10:37:09 +01:00
Toni Spets
037bde73a6
Upgrade Heisenbridge (1.9.0 -> 1.10.0) 2022-01-14 11:53:03 +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
Toni Spets
cdf76bdbb7
Upgrade Heisenbridge (1.8.2 -> 1.9.0) 2021-12-29 21:05:41 +02:00
Toni Spets
5df486f31e
Upgrade Heisenbridge (1.8.0 -> 1.8.2) 2021-12-25 18:05:41 +02:00
Toni Spets
061d6ac86f
Upgrade Heisenbridge (1.7.1 -> 1.8.0) 2021-12-22 19:04:21 +02:00
Toni Spets
e8a57ad432 Upgrade Heisenbridge (1.7.0 -> 1.7.1) 2021-11-23 15:03:09 +02:00
Toni Spets
110d91b06e Upgrade Heisenbridge (1.6.0 -> 1.7.0) 2021-11-18 13:05:30 +02:00
Toni Spets
f01b9c3865 Upgrade Heisenbridge (1.5.0 -> 1.6.0) 2021-11-12 04:50:29 +02:00
Slavi Pantaleev
735c966ab6 Disable systemd services when stopping to uninstall them
Until now, we were leaving services "enabled"
(symlinks in /etc/systemd/system/multi-user.target.wants/).

We clean these up now. Broken symlinks may still exist in older
installations that enabled/disabled services. We're not taking care
to fix these up. It's just a cosmetic defect anyway.
2021-11-10 17:39:21 +02:00
Toni Spets
09ac6a0e8c Upgrade Heisenbridge (1.4.1 -> 1.5.0) 2021-11-05 10:31:31 +02:00
Toni Spets
17fc055d53
Upgrade Heisenbridge (1.4.0 -> 1.4.1) 2021-10-31 18:31:31 +02:00
Toni Spets
124b9608fc Upgrade Heisenbridge (1.3.0 -> 1.4.0) 2021-10-28 21:07:11 +03:00
Toni Spets
d7af78066b Upgrade Heisenbridge (1.2.1 -> 1.3.0) 2021-10-21 19:55:13 +03:00
Toni Spets
3119ef4574 Upgrade Heisenbridge (1.2.0 -> 1.2.1) 2021-09-30 08:42:58 +03:00
Toni Spets
ff63f4efce Upgrade Heisenbridge (1.1.1 -> 1.2.0) 2021-09-23 10:18:46 +03:00
Toni Spets
8b9c7b18ac Upgrade Heisenbridge (1.1.0 -> 1.1.1) 2021-09-17 21:31:02 +03:00
Toni Spets
4adbefab82 Upgrade Heisenbridge (1.0.1 -> 1.1.0) 2021-09-14 11:17:28 +03:00
Toni Spets
c228343339 Bump Heisenbridge to v1.0.1 2021-09-03 07:58:48 +03:00
Toni Spets
4fe27a7645 Pin Heisenbridge to 1.0.0 2021-08-17 07:50:53 +03:00
Michael Sasser
7578a355c4
heisenbridge fix service name 2021-06-29 12:15:03 +02:00
Toni Spets
3581e1b37b Heisenbridge identd on unprivileged port
Fixes running the container as an unprivileged user.
2021-05-31 08:43:57 +03:00
Toni Spets
544915ff76 Add Heisenbridge 2021-05-19 10:42:21 +03:00