Commit Graph

105 Commits

Author SHA1 Message Date
c29a39a6fb Update Element 1.11.4 -> 1.11.5 2022-09-13 13:49:39 +00:00
a6ad396cd2 Update Element 1.11.3 -> 1.11.4 2022-08-31 16:35:37 +00:00
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
2022-08-24 17:08:53 +03:00
7f4200acc1 Update Element 1.11.2 -> 1.11.3 2022-08-16 15:37:43 +00:00
311926cbda Update Element 1.11.1 -> 1.11.2 2022-08-03 08:38:15 +00:00
a1469c8e14 Update Element v1.11.0 -> v1.11.1 2022-07-26 16:08:04 +00:00
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.
2022-07-18 16:43:12 +03:00
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.
2022-07-18 14:43:52 +03:00
d073c7ecb3 More ansible-lint fixes 2022-07-18 13:01:19 +03:00
ddf18eadc7 More ansible-lint fixes 2022-07-18 13:01:17 +03:00
34cdaade08 Use fully-qualified module names for builtin Ansible modules
Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939
2022-07-18 12:58:41 +03:00
e149f33140 add/unify 'Project source code URL' link across all roles 2022-07-16 23:59:21 +03:00
95fd215521 Update element 1.10.15 -> 1.11.0 2022-07-05 15:11:52 +00:00
b2f9ede87c Update Element v1.10.14 -> v1.10.15 2022-06-14 13:45:46 +00:00
4a72c90a6b Upgrade Element (v1.10.13 -> v1.10.14) 2022-06-07 14:34:02 +03:00
e37bcd1daf Updated Element 1.10.12 -> 1.10.13 2022-05-24 14:14:41 +00:00
2a9b52a1c2 Update Element self build repo URL
It forwards to the correct place but might as well just update it to the current URL.
2022-05-16 04:29:29 +00:00
02d4a841c4 Update Element 1.10.11 -> 1.10.12 2022-05-10 14:31:41 +00:00
4f1f3555f2 Update element 1.10.10 -> 1.10.11 2022-04-26 16:10:36 +00:00
5611cab71a Update element 1.10.9 -> 1.10.10 2022-04-14 13:38:38 -04:00
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
2022-04-14 08:52:37 +03:00
10c6c24c16 Update element 1.10.8 -> 1.10.9 2022-04-12 11:15:11 +00:00
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
f29f51a54c Update Element 1.10.7 -> 1.10.8 2022-03-28 13:52:44 -04:00
2da3768b20 Added retries to the docker pulls (#1701) 2022-03-17 17:37:11 +02:00
332fda6b02 Update Element 1.10.6 -> 1.10.7 2022-03-15 18:20:13 +00:00
42a8fb3a3c Upgrade Element (1.10.5 -> 1.10.6) 2022-03-01 17:30:15 -05:00
7384772957 Upgrade Element (1.10.4 -> 1.10.5) 2022-03-01 02:50:17 -05:00
a6e766a06a Upgrade Element (1.10.3 -> 1.10.4) 2022-02-18 19:56:22 +02:00
8b3fad45f9 Upgrade Element (1.10.1 -> 1.10.3)
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1627
2022-02-15 14:04:08 +02:00
819574b8ba Merge branch 'spantaleev:master' into master 2022-02-05 21:37:53 +01:00
7e5b88c3b7 fix: all praise the allmighty yamllinter 2022-02-05 21:32:54 +01:00
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
133d85fedf Upgrade Element (1.10.0 -> 1.10.1) 2022-02-01 18:27:06 +02:00
4216807c86 Upgrade Element (1.9.9 -> 1.10.0) 2022-01-31 18:51:28 +02:00
3614903e38 Updated: element-web to v1.9.9 2022-01-17 18:40:44 +01:00
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
dad1a23aa8 Update Element version (v1.9.7 -> v1.9.8) 2021-12-20 17:44:08 +01:00
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
2021-12-13 15:55:40 +00:00
391e095cb9 Update main.yml 2021-12-06 19:56:13 +01:00
e11e31e2c6 Update main.yml 2021-11-22 16:53:20 +01:00
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
367cddb715 Upgrade Element (v1.9.4) 2021-11-09 15:01:18 +01:00
0434e3bf8f Allow force-patching webpack.config.js when self-building Element
We were applying the low-memory system patch to webpack.config.js
on systems with < 4GB memory.

From now on, we also let people force-enable patching by toggling the
`matrix_client_element_container_image_self_build_low_memory_system_patch_enabled`
variable.

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357
2021-11-01 09:08:18 +02:00
c8a8035de4 Make it possible to self-build Element on low-memory devices (<4G RAM)
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1357
2021-10-29 11:13:01 +03:00
39fa852ed6 Remove unnecessary if checks
Should have been done in 63f5a88fa0.
2021-10-29 10:41:11 +03:00
63f5a88fa0 Separate install/uninstall tasks for Element and Hydrogen 2021-10-29 10:29:54 +03:00
d31cdb071a Upgrade Element (v1.9.3)
https://github.com/vector-im/element-web/releases/tag/v1.9.3
2021-10-25 12:44:58 -04:00
8c15555d00 Upgrade Element (1.9.0 -> 1.9.2) 2021-10-15 09:27:26 +03:00
Oli
59d4532efb Upgrade Element (1.8.5 -> 1.9.0) 2021-09-28 07:40:00 +02:00