9 Commits (5d10001712991f03f5b8a85530a814ac433a54a5)

Author	SHA1	Message	Date
Slavi Pantaleev	910cd9adf0	Replace import_role calls with include_role calls	2 years ago
Slavi Pantaleev	2688e8bfc3	Optimize initial installation by not reloading systemd after each .service install ... We expect `--tags=start` to handle systemd reloading, so we don't need to do it manually each time we install/uninstall a .service file.	2 years ago
Slavi Pantaleev	a04f6f4e3d	Optimize uninstall tasks a bit ... - forego removing Docker images - it's not effective anyway, because it only removes the last version.. which is a drop in the bucket, usually - do not reload systemd - it's none of our business. `--tags=start`, etc., handle this - combine all uninstall tasks under a single block, which only runs if we detect traces (a leftover systemd .service file) of the component. If no such .service is detected, we skip them all. This may lead to incorect cleanup in rare cases, but is good enough for the most part.	2 years ago
Slavi Pantaleev	2e7b5c7b02	Untangle the setup import/include mess in matrix-synapse	2 years ago
Slavi Pantaleev	d29b0aeddb	Replace even more import_tasks calls with include_tasks	2 years ago
Slavi Pantaleev	2473cd655b	Include ensure_openssl_installed and ensure_fuse_installed utils in a more reliable way ... This fixes a regression since the change done in c1c152f7ac. When another role (say `matrix-jitsi`) included `roles/custom/matrix-base/tasks/util/ensure_openssl_installed.yml`, which then included `{{ role_path }}/tasks/util/ensure_openssl_installed_DISTRO.yml`, that `role_path` variable would end up being the parent role (`matrix-jitsi`) and not the `matrix-base` role, so we'd get a failure. An alternative solution may have been to avoid using `role_path`, but importing roles properly (like we've done in this patch) sounds like a better way. Unfortunately, `import_role` fails if `tasks_from` is something like `util/ensure_openssl_installed` (containing a `/`), so I had to move these utils out of `util/`. Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2228	2 years ago
Slavi Pantaleev	d3bd1ca024	matrix_*_retries_{count,delay} -> devture_playbook_help_*_retries_{count,delay}	2 years ago
Slavi Pantaleev	835d2e9581	matrix_systemd_path -> devture_systemd_docker_base_systemd_path (via com.devture.ansible.role.systemd_docker_base)	2 years ago
Slavi Pantaleev	410a915a8a	Move roles/matrix* to roles/custom/matrix* ... This paves the way for installing other roles into `roles/galaxy` using `ansible-galaxy`, similar to how it's done in: - https://github.com/spantaleev/gitea-docker-ansible-deploy - https://github.com/spantaleev/nextcloud-docker-ansible-deploy In the near future, we'll be removing a lot of the shared role code from here and using upstream roles for it. Some of the core `matrix-*` roles have already been extracted out into other reusable roles: - https://github.com/devture/com.devture.ansible.role.postgres - https://github.com/devture/com.devture.ansible.role.systemd_docker_base - https://github.com/devture/com.devture.ansible.role.timesync - https://github.com/devture/com.devture.ansible.role.vars_preserver - https://github.com/devture/com.devture.ansible.role.playbook_runtime_messages - https://github.com/devture/com.devture.ansible.role.playbook_help We just need to migrate to those.	2 years ago