73 Commits (8de4e061e1fb09d982cb47321a43c94481cbd213)

Author	SHA1	Message	Date
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
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
WobbelTheBear	e11e31e2c6	Update main.yml	3 years ago
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.	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
Slavi Pantaleev	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	3 years ago
Slavi Pantaleev	39fa852ed6	Remove unnecessary if checks ... Should have been done in 63f5a88fa0.	3 years ago
Slavi Pantaleev	63f5a88fa0	Separate install/uninstall tasks for Element and Hydrogen	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	fa76c1ee5b	Do not run self-build Ansible version-check, if component not enabled ... Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1108	4 years ago
Slavi Pantaleev	0648b1b618	Upgrade Element (1.7.28 -> 1.7.29)	4 years ago
Slavi Pantaleev	47b4608b96	Fail in a friendlier way when trying to self-build on Ansible <= 2.8 ... Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1070 Related discussion here: 1ab507349c (commitcomment-51108407)	4 years ago
Slavi Pantaleev	1ab507349c	Fix self-building for various components on Ansible < 2.8 ... Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/1070	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
Slavi Pantaleev	512f42aa76	Do not report docker kill/rm attempts as errors ... These are just defensive cleanup tasks that we run. In the good case, there's nothing to kill or remove, so they trigger an error like this: > Error response from daemon: Cannot kill container: something: No such container: something and: > Error: No such container: something People often ask us if this is a problem, so instead of always having to answer with "no, this is to be expected", we'd rather eliminate it now and make logs cleaner. In the event that: - a container is really stuck and needs cleanup using kill/rm - and cleanup fails, and we fail to report it because of error suppression (`2>/dev/null`) .. we'd still get an error when launching ("container name already in use .."), so it shouldn't be too hard to investigate.	4 years ago
throwawayay	a30ef0cc29	Update element-web (1.7.16 -> 1.7.17)	4 years ago