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
7e5b88c3b7
fix: all praise the allmighty yamllinter
2022-02-05 21:32:54 +01: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
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
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
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
59d4532efb
Upgrade Element (1.8.5 -> 1.9.0)
2021-09-28 07:40:00 +02:00
b166f0175a
Upgrade Element (1.8.4 -> 1.8.5)
2021-09-15 09:36:21 +03:00
4b46913278
Upgrade Element (1.8.2 -> 1.8.4) to patch a security issue
...
See:
- https://github.com/vector-im/element-web/releases/tag/v1.8.4
- https://matrix.org/blog/2021/09/10/pre-disclosure-upcoming-critical-fix-for-several-popular-matrix-clients
2021-09-13 16:24:09 +03:00
d384d0d7a0
Upgrade Element (1.8.1 -> 1.8.2)
2021-09-01 11:14:04 +03:00
12dbb29675
Upgrade Element (1.8.0 -> 1.8.1)
...
Element web/desktop has just been updated to fix some regressions in regard to VoIP.
2021-08-17 12:47:52 +02:00
70d412e523
Upgrade Element (1.7.34 -> 1.8.0)
2021-08-16 18:10:22 +03:00
5fc61ed964
Upgrade Element (1.7.33 -> 1.7.34)
2021-08-04 09:09:35 +03:00
70cb27138c
Upgrade Element (1.7.32 -> 1.7.33)
2021-07-19 18:57:19 +03:00
3fa895fe96
Upgrade Element (1.7.31 -> 1.7.32)
2021-07-09 11:26:13 +03:00
b19fa3acb2
Upgrade Element (1.7.30 -> 1.7.31)
2021-06-22 10:18:58 +03:00
77fd1bff22
Update element 1.7.29 -> 1.7.30
2021-06-08 14:57:49 +00:00
0648b1b618
Upgrade Element (1.7.28 -> 1.7.29)
2021-05-24 20:38:48 +03:00
400371f6dd
Updated Element version (1.7.27 -> 1.7.28)
2021-05-17 13:15:12 +00:00
f4657b2cdb
Upgrade Element (1.7.26 -> 1.7.27)
2021-05-11 08:22:43 +03:00
2409c33ea2
Upgrade Element (1.7.25 -> 1.7.26)
2021-04-27 17:21:31 +03:00
4f8e1bd43a
Updated Element Web 1.7.24.1 -> 1.7.25
2021-04-12 18:04:56 +00:00
e335f3fc77
rename matrix_global_registry to matrix_container_global_registry_prefix related to #990
...
Signed-off-by: Ahmad Haghighi <haghighi@fedoraproject.org >
2021-04-12 17:23:55 +04:30
f52a8b6484
use custom docker registry
2021-04-12 17:23:55 +04:30
81dddd2e25
Upgrade Element (1.7.24 -> 1.7.24.1)
2021-04-02 18:43:30 -05:00
5e1cf7f8b9
Upgrade Element (1.7.23 -> 1.7.24)
2021-03-29 17:58:02 +03:00
15fc7ac007
Updated Element 1.22 -> 1.23
2021-03-15 17:55:27 +02:00
c527f2930e
Upgrade Element (1.7.21 -> 1.7.22)
2021-03-01 15:53:54 +02:00
2f887f292c
added "matrix_%SERVICE%_version" variable to all roles, use it in "matrix_%SERVICE%_docker_image" var (preserving backward-compatibility)
2021-02-20 19:08:28 +02:00
865d71e35a
Upgrade Element (1.7.20 -> 1.7.21)
2021-02-16 13:44:28 +02:00
9ad67d7cdf
Upgrade Element (1.7.19 -> 1.7.20)
...
https://github.com/vector-im/element-web/releases/tag/v1.7.20
https://hub.docker.com/layers/vectorim/element-web/v1.7.20/images/sha256-44cae3a532d86c16940deb70866b522ba6acc8c5d7adf3c661cfc8b06f1de681?context=explore
2021-02-04 16:26:56 +02:00
5cb976c321
Upgrade Element (1.7.18 -> 1.7.19)
2021-02-03 10:07:43 -06:00
3ea90ca436
Upgrade Element (1.7.17 -> 1.7.18)
2021-01-28 09:23:23 +02:00
07f1ea24ee
Make it possible to override the welcome.html.j2 template used for Element
2021-01-27 12:36:57 +02:00
a30ef0cc29
Update element-web (1.7.16 -> 1.7.17)
2021-01-20 08:35:07 -05:00
c3b63c6c97
Update element-web (1.7.15 -> 1.7.16)
2020-12-22 08:29:37 -06:00
8c02f7b79b
Upgrade services
2020-12-07 15:18:03 +02:00
be5263f397
Move self-building git repository URLs to variables (stop hardcoding)
2020-11-28 21:34:14 +02:00
c9d2ef7981
Upgrade Element (1.7.13 -> 1.7.14)
2020-11-23 23:05:54 -06:00
5eed874199
Improve self-building experience (avoid conflict with pullable images)
...
Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/716
This patch makes us use more fully-qualified container image names
(either prefixed with docker.io/ or with localhost/).
The latter happens when self-building is enabled.
We've recently had issues where if an image was removed manually
and the service was restarted (making `docker run` fetch it from Docker Hub, etc.),
we'd end up with a pulled image, even though we're aiming for a self-built one.
Re-running the playbook would then not do a rebuild, because:
- the image with that name already exists (even though it's something
else)
- we sometimes had conditional logic where we'd build only if the git
repo changed
By explicitly changing the name of the images (prefixing with localhost/),
we avoid such confusion and the possibility that we'd automatically pul something
which is not what we expect.
Also, I've removed that condition where building would happen on git
changes only. We now always build (unless an image with that name
already exists). We just force-build when the git repo changes.
2020-11-14 23:00:49 +02:00
