self-hosted/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2024-12-12 08:43:55 +02:00
Code Issues Releases Activity
f8966cd8da
matrix-docker-ansible-deploy/requirements.yml

59 lines
2.0 KiB
YAML
Raw Normal View History

Initial work on using externally defined roles
2022-11-04 14:58:28 +02:00
---
Install Docker via geerlingguy.docker Galaxy role
2022-11-22 09:01:26 +02:00
- src: geerlingguy.docker
Upgrade geerlingguy.docker (6.0.4 -> 6.1.0)
2023-02-19 10:20:40 +02:00
version: 6.1.0
Install Docker via geerlingguy.docker Galaxy role
2022-11-22 09:01:26 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.docker_sdk_for_python.git
Upgrade com.devture.ansible.role.docker_sdk_for_python Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2522
2023-02-27 08:27:41 +02:00
version: 129c8590e106b83e6f4c259649a613c6279e937a
Install Docker via geerlingguy.docker Galaxy role
2022-11-22 09:01:26 +02:00
Initial work on using externally defined roles
2022-11-04 14:58:28 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.playbook_help.git
version: c1f40e82b4d6b072b6f0e885239322bdaaaf554f
- src: git+https://github.com/devture/com.devture.ansible.role.systemd_docker_base.git
version: 327d2e17f5189ac2480d6012f58cf64a2b46efba
Install ntpd/systemd-timesync via com.devture.ansible.role.timesync
2022-11-04 16:33:22 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.timesync.git
Upgrade com.devture.ansible.role.timesync
2023-01-17 14:51:00 +02:00
version: 3d5bb2976815958cdce3f368fa34fb51554f899b
Install ntpd/systemd-timesync via com.devture.ansible.role.timesync
2022-11-04 16:33:22 +02:00
Initial work on using externally defined roles
2022-11-04 14:58:28 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.playbook_state_preserver.git
Upgrade com.devture.ansible.role.playbook_state_preserver
2022-11-05 06:56:10 +02:00
version: ff2fd42e1c1a9e28e3312bbd725395f9c2fc7f16
Initial work on using externally defined roles
2022-11-04 14:58:28 +02:00
Switch from matrix-postgres to com.devture.ansible.role.postgres
2022-11-27 07:23:41 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.postgres.git
Upgrade com.devture.ansible.role.postgres
2023-01-13 18:12:22 +02:00
version: a1bb78d194434b38005f3a9e623bfa4b2c06c7bc
Switch from matrix-postgres to com.devture.ansible.role.postgres
2022-11-27 07:23:41 +02:00
Replace custom/matrix-postgres-backup role with galaxy/com.devture.ansible.role.postgres_backup This role is usable on its own and it's not tied to Matrix, so extracting it out into an independent role that we install via ansible-galaxy makes sense. This also fixes the confusion from the other day, where `matrix_postgres_*` had to be renamed to `devture_postgres_*` (unless it was about `matrix_postgres_backup_*`). We now can safely say that ALL `matrix_postgres_*` variables need to be renamed. Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2305
2022-11-30 10:59:25 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.postgres_backup.git
Upgrade com.devture.ansible.role.postgres_backup
2023-03-03 09:04:13 +02:00
version: 8e9ec48a09284c84704d7a2dce17da35f181574d
Replace custom/matrix-postgres-backup role with galaxy/com.devture.ansible.role.postgres_backup This role is usable on its own and it's not tied to Matrix, so extracting it out into an independent role that we install via ansible-galaxy makes sense. This also fixes the confusion from the other day, where `matrix_postgres_*` had to be renamed to `devture_postgres_*` (unless it was about `matrix_postgres_backup_*`). We now can safely say that ALL `matrix_postgres_*` variables need to be renamed. Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2305
2022-11-30 10:59:25 +02:00
Replace matrix-common-after systemd service management with com.devture.ansible.role.systemd_service_manager
2022-11-23 10:14:28 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.systemd_service_manager.git
Replace most import_tasks calls with include_tasks for improved performance
2022-11-24 11:33:30 +02:00
version: 6ccb88ac5fc27e1e70afcd48278ade4b564a9096
Replace matrix-common-after systemd service management with com.devture.ansible.role.systemd_service_manager
2022-11-23 10:14:28 +02:00
Initial work on using externally defined roles
2022-11-04 14:58:28 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.playbook_runtime_messages.git
Replace most import_tasks calls with include_tasks for improved performance
2022-11-24 11:33:30 +02:00
version: 9b4b088c62b528b73a9a7c93d3109b091dd42ec6
Switch from matrix-prometheus-node-exporter to an external prometheus_node_exporter role
2023-01-21 11:07:04 +02:00
- src: git+https://gitlab.com/etke.cc/roles/prometheus_node_exporter.git
Upgrade prometheus_node_exporter (v1.5.0-1 -> v1.5.0-2)
2023-02-06 09:54:34 +02:00
version: v1.5.0-2
Switch from matrix-prometheus-postgres-exporter to an external prometheus_postgres_exporter role
2023-02-05 10:32:09 +02:00
- src: git+https://gitlab.com/etke.cc/roles/prometheus_postgres_exporter.git
Upgrade prometheus_postgres_exporter (v0.11.1-1 -> v0.11.1-2)
2023-02-06 09:49:15 +02:00
version: v0.11.1-2
Initial work on Traefik support This gets us started on adding a Traefik role and hooking Traefik: - directly to services which support Traefik - we only have a few of these right now, but the list will grow - to matrix-nginx-proxy for most services that integrate with matrix-nginx-proxy right now Traefik usage should be disabled by default for now and nothing should change for people just yet. Enabling these experiments requires additional configuration like this: ```yaml devture_traefik_ssl_email_address: '.....' matrix_playbook_traefik_role_enabled: true matrix_playbook_traefik_labels_enabled: true matrix_ssl_retrieval_method: none matrix_nginx_proxy_https_enabled: false matrix_nginx_proxy_container_http_host_bind_port: '' matrix_nginx_proxy_container_federation_host_bind_port: '' matrix_nginx_proxy_trust_forwarded_proto: true matrix_nginx_proxy_x_forwarded_for: '$proxy_add_x_forwarded_for' matrix_coturn_enabled: false ``` What currently works is: reverse-proxying for all nginx-proxy based services **except** for the Matrix homeserver (both Client-Server an Federation traffic for the homeserver don't work yet)
2023-02-06 10:34:51 +02:00
Replace matrix-backup-borg with an external role
2023-02-13 10:53:11 +02:00
- src: git+https://gitlab.com/etke.cc/roles/backup_borg.git
update borgmatic 1.7.7 -> 1.7.8
2023-03-03 08:21:26 +02:00
version: v1.2.3-1.7.8-0
Replace matrix-backup-borg with an external role
2023-02-13 10:53:11 +02:00
Replace matrix-grafana with an external role
2023-02-15 10:30:58 +02:00
- src: git+https://gitlab.com/etke.cc/roles/grafana.git
update grafana 9.4.1 -> 9.4.2
2023-03-03 08:18:52 +02:00
version: v9.4.2-0
Replace matrix-grafana with an external role
2023-02-15 10:30:58 +02:00
Switch to using an external Ntfy role The newly extracted role also has native Traefik support, so we no longer need to rely on `matrix-nginx-proxy` for reverse-proxying to Ntfy. The new role uses port `80` inside the container (not `8080`, like before), because that's the default assumption of the officially published container image. Using a custom port (like `8080`), means the default healthcheck command (which hardcodes port `80`) doesn't work. Instead of fiddling to override the healthcheck command, we've decided to stick to the default port instead. This only affects the inside-the-container port, not any external ports. The new role also supports adding the network ranges of the container's multiple additional networks as "exempt hosts". Previously, only one network's address range was added to "exempt hosts".
2023-02-17 09:54:33 +02:00
- src: git+https://gitlab.com/etke.cc/roles/ntfy.git
update ntfy 2.1.0 -> 2.1.1
2023-03-01 22:09:54 +02:00
version: v2.1.1-0
Switch to using an external Ntfy role The newly extracted role also has native Traefik support, so we no longer need to rely on `matrix-nginx-proxy` for reverse-proxying to Ntfy. The new role uses port `80` inside the container (not `8080`, like before), because that's the default assumption of the officially published container image. Using a custom port (like `8080`), means the default healthcheck command (which hardcodes port `80`) doesn't work. Instead of fiddling to override the healthcheck command, we've decided to stick to the default port instead. This only affects the inside-the-container port, not any external ports. The new role also supports adding the network ranges of the container's multiple additional networks as "exempt hosts". Previously, only one network's address range was added to "exempt hosts".
2023-02-17 09:54:33 +02:00
Switch to using an external Redis role
2023-02-17 16:23:59 +02:00
- src: git+https://gitlab.com/etke.cc/roles/redis.git
Upgrade Redis (v7.0.7-0 -> v7.0.9-0)
2023-03-01 10:30:09 +02:00
version: v7.0.9-0
Switch to using an external Redis role
2023-02-17 16:23:59 +02:00
Switch to using an external Etherpad role This new role also adds native Traefik support and support for other (non-`amd64`) architectures via self-building.
2023-03-02 22:50:13 +02:00
- src: git+https://gitlab.com/etke.cc/roles/etherpad.git
Upgrade Etherpad role (v1.8.18-1 -> v1.8.18-2)
2023-03-02 23:00:18 +02:00
version: v1.8.18-2
Switch to using an external Etherpad role This new role also adds native Traefik support and support for other (non-`amd64`) architectures via self-building.
2023-03-02 22:50:13 +02:00
Initial work on Traefik support This gets us started on adding a Traefik role and hooking Traefik: - directly to services which support Traefik - we only have a few of these right now, but the list will grow - to matrix-nginx-proxy for most services that integrate with matrix-nginx-proxy right now Traefik usage should be disabled by default for now and nothing should change for people just yet. Enabling these experiments requires additional configuration like this: ```yaml devture_traefik_ssl_email_address: '.....' matrix_playbook_traefik_role_enabled: true matrix_playbook_traefik_labels_enabled: true matrix_ssl_retrieval_method: none matrix_nginx_proxy_https_enabled: false matrix_nginx_proxy_container_http_host_bind_port: '' matrix_nginx_proxy_container_federation_host_bind_port: '' matrix_nginx_proxy_trust_forwarded_proto: true matrix_nginx_proxy_x_forwarded_for: '$proxy_add_x_forwarded_for' matrix_coturn_enabled: false ``` What currently works is: reverse-proxying for all nginx-proxy based services **except** for the Matrix homeserver (both Client-Server an Federation traffic for the homeserver don't work yet)
2023-02-06 10:34:51 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.traefik.git
Upgrade com.devture.ansible.role.traefik
2023-03-03 08:58:23 +02:00
version: v2.9.8-0
Add com.devture.ansible.role.traefik_certs_dumper role With this, other roles (like Coturn, Postmoogle) will be able to use SSL certificates extracted from Traefik via https://github.com/ldez/traefik-certs-dumper
2023-02-08 16:05:38 +02:00
- src: git+https://github.com/devture/com.devture.ansible.role.traefik_certs_dumper.git
Upgrade com.devture.ansible.role.traefik_certs_dumper
2023-03-03 08:59:57 +02:00
version: v2.8.1-0
Reference in New Issue Copy Permalink