Aine
501420f3cc
Update element 1.11.12 -> 1.11.13
2 years ago
Sebastian Gumprich
48388a3d96
use fqcns for some task
...
Signed-off-by: Sebastian Gumprich <github@gumpri.ch>
2 years ago
Joe Kappus
170960be1a
update element v1.11.11 -> v1.11.12
...
fixes jitsi issue
2 years ago
Aine
437d177d31
update element v1.11.10 -> v1.11.11
2 years ago
Aine
3c669761ce
Update element 1.11.9 -> 1.11.10
2 years ago
Aine
19f1c8ea5e
Update element 1.11.8 -> 1.11.9
2 years ago
Slavi Pantaleev
68c2e0bee5
Upgrade Element (v1.11.7 -> v1.11.8)
2 years ago
Julian-Samuel Gebühr
38e19e48d2
Bump element version
...
This is a security relevant update
2 years ago
Aine
f9e750c47f
Update Element 1.11.5 -> 1.11.6
2 years ago
Slavi Pantaleev
1ea1597020
Fix some ansible-lint-reported warnings
...
This mostly fixes `key-order` warnings around
`block` statements.
2 years ago
Aine
c29a39a6fb
Update Element 1.11.4 -> 1.11.5
2 years ago
Aine
a6ad396cd2
Update Element 1.11.3 -> 1.11.4
2 years ago
Slavi Pantaleev
b196e15796
Fix incorrectly named module arguments (ansible.builtin.group -> group)
...
Regression since the mass-replace in 34cdaade0
.
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2054
2 years ago
Aine
7f4200acc1
Update Element 1.11.2 -> 1.11.3
2 years ago
Aine
311926cbda
Update Element 1.11.1 -> 1.11.2
2 years ago
Aine
a1469c8e14
Update Element v1.11.0 -> v1.11.1
2 years ago
Slavi Pantaleev
c73680712b
Fix (suppress) var-naming ansible-lint errors
...
Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#var-naming
We don't really fix these, but just suppress them,
because they're like that intentionally.
We try to name variables in a way that is consistent with the
configuration key they control. If the upstream component uses
camelCase, we also need to include camelCase in the variable name.
2 years ago
Slavi Pantaleev
0ab2001ce7
Fix git-latest ansible-lint errors
...
Reference: https://ansible-lint.readthedocs.io/en/latest/default_rules/#git-latest
Our variable naming is not necessarily consistent across roles.
I've tried to follow the naming conventions of each individual role.
All new variables are suffixed with `_version`, but the prefix may be
somewhat different.
2 years ago
Slavi Pantaleev
d073c7ecb3
More ansible-lint fixes
2 years ago
Slavi Pantaleev
ddf18eadc7
More ansible-lint fixes
2 years ago
Slavi Pantaleev
34cdaade08
Use fully-qualified module names for builtin Ansible modules
...
Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939
2 years ago
Aine
e149f33140
add/unify 'Project source code URL' link across all roles
2 years ago
Aine
95fd215521
Update element 1.10.15 -> 1.11.0
2 years ago
Aine
b2f9ede87c
Update Element v1.10.14 -> v1.10.15
2 years ago
Slavi Pantaleev
4a72c90a6b
Upgrade Element (v1.10.13 -> v1.10.14)
3 years ago
Aine
e37bcd1daf
Updated Element 1.10.12 -> 1.10.13
3 years ago
Aaron Raimist
2a9b52a1c2
Update Element self build repo URL
...
It forwards to the correct place but might as well just update it to the current URL.
3 years ago
Aine
02d4a841c4
Update Element 1.10.11 -> 1.10.12
3 years ago
Aine
4f1f3555f2
Update element 1.10.10 -> 1.10.11
3 years ago
joecool1029
5611cab71a
Update element 1.10.9 -> 1.10.10
3 years ago
Slavi Pantaleev
2df993977a
Ensure git cloning when self-building is done with the matrix user, not root
...
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1749
3 years ago
Aine
10c6c24c16
Update element 1.10.8 -> 1.10.9
3 years ago
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".
3 years ago
joecool1029
f29f51a54c
Update Element 1.10.7 -> 1.10.8
3 years ago
Aine
2da3768b20
Added retries to the docker pulls ( #1701 )
3 years ago
Aine
332fda6b02
Update Element 1.10.6 -> 1.10.7
3 years ago
joecool1029
42a8fb3a3c
Upgrade Element (1.10.5 -> 1.10.6)
3 years ago
joecool1029
7384772957
Upgrade Element (1.10.4 -> 1.10.5)
3 years ago
Christos Karamolegkos
a6e766a06a
Upgrade Element (1.10.3 -> 1.10.4)
3 years ago
Slavi Pantaleev
8b3fad45f9
Upgrade Element (1.10.1 -> 1.10.3)
...
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1627
3 years ago
Marko Weltzer
819574b8ba
Merge branch 'spantaleev:master' into master
3 years ago
Marko Weltzer
7e5b88c3b7
fix: all praise the allmighty yamllinter
3 years ago
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.
3 years ago
Slavi Pantaleev
133d85fedf
Upgrade Element (1.10.0 -> 1.10.1)
3 years ago
Slavi Pantaleev
4216807c86
Upgrade Element (1.9.9 -> 1.10.0)
3 years ago
GoliathLabs
3614903e38
Updated: element-web to v1.9.9
3 years ago
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=
3 years ago
WobbelTheBear
dad1a23aa8
Update Element version (v1.9.7 -> v1.9.8)
3 years ago
rakshazi
1f0d56fb75
(Security fix) Update Element 1.9.6 -> 1.9.7
...
Ref: https://matrix.org/blog/2021/12/13/disclosure-buffer-overflow-in-libolm-and-matrix-js-sdk
3 years ago
WobbelTheBear
391e095cb9
Update main.yml
3 years ago