iartamonov/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-07-19 13:46:19 +03:00
Code Issues Packages Projects Releases Wiki Activity
10,572 Commits 12 Branches 0 Tags
4f6293ecb80fade1ec284901e9900c904d5e3b8a
Commit Graph
17 Commits
Author SHA1 Message Date
Aine 16212150a3 Sygnal: rollback to v0.15.1, because v0.16.0's docker image is broken
Lock Threads / action (push) Has been cancelled
Matrix CI / yamllint (push) Has been cancelled
Matrix CI / ansible-lint (push) Has been cancelled
Matrix CI / Run pre-commit (push) Has been cancelled
Close stale issues and PRs / stale (push) Has been cancelled
2025-07-24 16:47:36 +01:00
renovate[bot]andSlavi Pantaleev 69184bc4a3 Update matrixdotorg/sygnal Docker tag to v0.16.0 2025-07-24 12:39:35 +03:00
Suguru Hirahara 9bb3d2457c Add license information to files for matrix-sygnal 
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
 2025-02-27 18:32:26 +09:00
Slavi Pantaleev c47eca389b Rework all roles to include component_(docker|container)_image_registry_prefix* variables 
This:

- brings consistency - no more mixing `_name_prefix` and `_registry_prefix`
- adds extensibility - a future patch will allow reconfiguring all registry prefixes for all roles in the playbook

We still have `_docker_` vs `_container_` inconsistencies.
These may be worked on later.
 2025-02-24 11:38:47 +02:00
Slavi Pantaleev d6bf789710 Remove matrix_container_global_registry_prefix variable 
This is done for a few reasons:

- less globals and more indepdendence for each role is better. We rely
  on various externally-hosted roles and they don't rely on this global
  either.

- `matrix_container_global_registry_prefix` could make people think they
  could just override this variable and have all their images pull from
  elsewhere. This is rarely the case, unless you've taken special care
  to mirror all the various components (from their respective
  registries) to your own. In such a case, you probably know what you're
  mirroring and can adjust individual variables.

- nowadays, various components live on different registries.
  With Docker Inc tightening rate limits for Docker Hub, it's even more
  likely that we'll see increased diversity in where images are hosted
 2025-02-23 10:15:41 +02:00
Suguru HiraharaGitHubSuguru Hirahara
 		99f4af2007 Update files for Sygnal (#3958) 
* Rename sygnal.yaml.j2 to config.yaml.j2

There does not seem to exist other yaml.j2 files, which would be named after the servive.

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

* Update docs/configuring-playbook-sygnal.md: add the section "Extending the configuration"

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>

---------

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Co-authored-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
 2025-01-18 09:15:04 +02:00
renovate[bot]andGitHub cf29bc7511 Update matrixdotorg/sygnal Docker tag to v0.15.1 2024-10-04 13:06:19 +00:00
renovate[bot]andGitHub 659df10799 chore(deps): update matrixdotorg/sygnal docker tag to v0.15.0 2024-06-26 16:20:10 +00:00
Slavi Pantaleev 9f2eff2ac7 Respect devture_systemd_docker_base_docker_service_name 
Related to https://github.com/devture/com.devture.ansible.role.systemd_docker_base/commit/0241c71a4c08ff5e203b55d50a424387e3b077c8

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3270#issuecomment-2143782962

With this change, it should be possible for people to adjust the Docker
dependency from `docker.service` to something else (e.g. `pkg-ContainerManager-dockerd.service`),
or to completely eliminate it by setting `devture_systemd_docker_base_docker_service_name` to an empty string.

This makes it easier for people to use the playbook against a Synology DSM server.
 2024-06-04 13:14:34 +03:00
renovate[bot]andGitHub 5997658348 chore(deps): update matrixdotorg/sygnal docker tag to v0.14.3 2024-05-31 23:04:46 +00:00
renovate[bot]andGitHub 3af2624b2b chore(deps): update matrixdotorg/sygnal docker tag to v0.14.2 2024-05-22 03:06:59 +00:00
renovate[bot]andGitHub a57b38dc25 chore(deps): update matrixdotorg/sygnal docker tag to v0.14.1 2024-04-09 19:56:18 +00:00
renovate[bot]andGitHub 6d1fdce34a chore(deps): update matrixdotorg/sygnal docker tag to v0.14.0 2024-03-21 16:06:43 +00:00
renovate[bot]andGitHub ba0d86370a Update matrixdotorg/sygnal Docker tag to v0.13.0 2023-11-21 16:55:17 +00:00
Samuel Meenzen c846ed199b Annotate version numbers with renovate metadata 2023-10-06 14:14:03 +02:00
Slavi Pantaleev d20ff688db Add native Traefik support to Sygnal 2023-02-26 11:03:42 +02:00
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.
 2022-11-03 09:11:29 +02:00