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
7e5b88c3b7
fix: all praise the allmighty yamllinter
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
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
WobbelTheBear
e11e31e2c6
Update main.yml
3 years ago
teutat3s
367cddb715
Upgrade Element (v1.9.4)
3 years ago
Slavi Pantaleev
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
3 years ago
throwawayay
d31cdb071a
Upgrade Element (v1.9.3)
...
https://github.com/vector-im/element-web/releases/tag/v1.9.3
3 years ago
Slavi Pantaleev
8c15555d00
Upgrade Element (1.9.0 -> 1.9.2)
3 years ago
Oli
59d4532efb
Upgrade Element (1.8.5 -> 1.9.0)
3 years ago
Slavi Pantaleev
b166f0175a
Upgrade Element (1.8.4 -> 1.8.5)
3 years ago
Slavi Pantaleev
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
3 years ago
Slavi Pantaleev
d384d0d7a0
Upgrade Element (1.8.1 -> 1.8.2)
3 years ago
WobbelTheBear
12dbb29675
Upgrade Element (1.8.0 -> 1.8.1)
...
Element web/desktop has just been updated to fix some regressions in regard to VoIP.
3 years ago
Slavi Pantaleev
70d412e523
Upgrade Element (1.7.34 -> 1.8.0)
3 years ago
Slavi Pantaleev
5fc61ed964
Upgrade Element (1.7.33 -> 1.7.34)
3 years ago
Slavi Pantaleev
70cb27138c
Upgrade Element (1.7.32 -> 1.7.33)
3 years ago
Slavi Pantaleev
3fa895fe96
Upgrade Element (1.7.31 -> 1.7.32)
3 years ago
Slavi Pantaleev
b19fa3acb2
Upgrade Element (1.7.30 -> 1.7.31)
3 years ago
rakshazi
77fd1bff22
Update element 1.7.29 -> 1.7.30
4 years ago
Slavi Pantaleev
0648b1b618
Upgrade Element (1.7.28 -> 1.7.29)
4 years ago
rakshazi
400371f6dd
Updated Element version (1.7.27 -> 1.7.28)
4 years ago
Slavi Pantaleev
f4657b2cdb
Upgrade Element (1.7.26 -> 1.7.27)
4 years ago
Slavi Pantaleev
2409c33ea2
Upgrade Element (1.7.25 -> 1.7.26)
4 years ago
rakshazi
4f8e1bd43a
Updated Element Web 1.7.24.1 -> 1.7.25
4 years ago
Ahmad Haghighi
e335f3fc77
rename matrix_global_registry to matrix_container_global_registry_prefix related to #990
...
Signed-off-by: Ahmad Haghighi <haghighi@fedoraproject.org>
4 years ago
Ahmad Haghighi
f52a8b6484
use custom docker registry
4 years ago
Aaron Raimist
81dddd2e25
Upgrade Element (1.7.24 -> 1.7.24.1)
4 years ago
Slavi Pantaleev
5e1cf7f8b9
Upgrade Element (1.7.23 -> 1.7.24)
4 years ago
rakshazi
15fc7ac007
Updated Element 1.22 -> 1.23
4 years ago
Slavi Pantaleev
c527f2930e
Upgrade Element (1.7.21 -> 1.7.22)
4 years ago
rakshazi
2f887f292c
added "matrix_%SERVICE%_version" variable to all roles, use it in "matrix_%SERVICE%_docker_image" var (preserving backward-compatibility)
4 years ago
Slavi Pantaleev
865d71e35a
Upgrade Element (1.7.20 -> 1.7.21)
4 years ago
Paul Tötterman
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
4 years ago
Aaron Raimist
5cb976c321
Upgrade Element (1.7.18 -> 1.7.19)
4 years ago
Slavi Pantaleev
3ea90ca436
Upgrade Element (1.7.17 -> 1.7.18)
4 years ago
Slavi Pantaleev
07f1ea24ee
Make it possible to override the welcome.html.j2 template used for Element
4 years ago
throwawayay
a30ef0cc29
Update element-web (1.7.16 -> 1.7.17)
4 years ago
Dan Arnfield
c3b63c6c97
Update element-web (1.7.15 -> 1.7.16)
4 years ago
Slavi Pantaleev
8c02f7b79b
Upgrade services
4 years ago
Slavi Pantaleev
be5263f397
Move self-building git repository URLs to variables (stop hardcoding)
4 years ago
Aaron Raimist
c9d2ef7981
Upgrade Element (1.7.13 -> 1.7.14)
4 years ago
Slavi Pantaleev
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.
4 years ago