finallycoffee/matrix-docker-ansible-deploy
finallycoffee/matrix-docker-ansible-deploy
2
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
3eae4384dc
matrix-docker-ansible-deploy/setup.yml

160 lines
5.0 KiB
YAML
Raw Normal View History

Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
---
- name: "Set up a Matrix server"
hosts: "{{ target if target is defined else 'matrix_servers' }}"
become: true
roles:
# Most of the roles below are not distributed with the playbook, but downloaded separately using `ansible-galaxy` via the `just roles` command (see `justfile`).
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/playbook_help
Upgrade playbook_help Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2448
2024-01-23 06:58:25 +00:00
tags:
- setup-all
- install-all
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/systemd_docker_base
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- role: custom/matrix_playbook_migration
- when: matrix_playbook_docker_installation_enabled | bool
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
role: galaxy/docker
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
vars:
docker_install_compose: false
Do not install docker compose plugin Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2924 Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2922
2023-10-02 04:02:45 +00:00
docker_install_compose_plugin: false
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
tags:
- setup-docker
- setup-all
- install-docker
- install-all
- when: devture_docker_sdk_for_python_installation_enabled | bool
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
role: galaxy/docker_sdk_for_python
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
tags:
- setup-docker
- setup-all
- install-docker
- install-all
- when: devture_timesync_installation_enabled | bool
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
role: galaxy/timesync
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
tags:
- setup-timesync
- setup-all
- install-timesync
- install-all
- custom/matrix-base
- custom/matrix-dynamic-dns
Replace matrix-mailer with an external role
2024-01-05 15:54:50 +00:00
- galaxy/exim_relay
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/postgres
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- galaxy/redis
Add keydb (#3244) * add keydb as redis replacement * sort requirements
2024-03-26 09:25:18 +00:00
- galaxy/keydb
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-corporal
Add support for D4A/Draupnir For All to the playbook. (#3204) * Draupnir for all Role * Draupnir for all Documentation * Pin D4A to Develop until D4A patches are in a release. * Update D4A Docs to mention pros and cons of D4A mode compared to normal * Change Documentation to mention a fixed simpler provisioning flow. Use of /plain allows us to bypass the bugs encountered during the development of this role with clients attempting to escape our wildcards causing the grief that led to using curl. This reworded commit does still explain you can automatically inject stuff into the room if you wanted to. * Emphasise the State of D4A mode * Link to Draupnir-for-all docs and tweak the docs some * Link to Draupnir-for-all from Draupnir documentation page * Announce Draupnir-for-all --------- Co-authored-by: Slavi Pantaleev <slavi@devture.com>
2024-03-05 14:09:52 +00:00
- custom/matrix-appservice-draupnir-for-all
Add appservice-double-puppet service for better bridge double-puppeting Bridges will be switched to this new method in future patches.
2024-08-17 16:00:16 +00:00
- custom/matrix-appservice-double-puppet
Add support for matrix-alertmanager-receiver
2024-07-06 18:48:41 +00:00
- custom/matrix-alertmanager-receiver
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-bridge-appservice-discord
- custom/matrix-bridge-appservice-slack
- custom/matrix-bridge-appservice-webhooks
- custom/matrix-bridge-appservice-irc
- custom/matrix-bridge-appservice-kakaotalk
- custom/matrix-bridge-beeper-linkedin
- custom/matrix-bridge-go-skype-bridge
Add support for WeChat bridging This is based on the PR (https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/3241) by Tobias Diez (https://github.com/tobiasdiez). I've refactored some parts, made it more configurable, polished it up, and it's integrated into the playbook now. Both the WeChat bridge and WeChat agent appear to be working. The WeChat bridge joins rooms and responds as expected. That said, end-to-end testing (actually bridging to a WeChat account) has not been done yet. Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/701 Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3092 This is sponsored https://etke.cc/ work related to https://gitlab.com/etke.cc/ansible/-/issues/2 Squashed commit of the following: commit fdd37f02472a0b83d61b4fac80650442f90e7629 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 21:05:53 2024 +0300 Add documentation for WeChat bridge commit 8426fc8b95bb160ea7f9659bd45bc59cf1326614 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 20:59:42 2024 +0300 Rename directory for matrix_wechat_agent_container_src_files_path commit da200df82bbc9153d307095dd90e4769c400ea1e Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 20:58:26 2024 +0300 Make WeChat listen_secret configurable and auto-configured via matrix_homeserver_generic_secret_key commit 4022cb1355828ac16af7d9228cb1066962bb35f5 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 20:54:56 2024 +0300 Refactor install.yml for WeChat a bit (using blocks, etc.) commit d07a39b4c4f6b93d04204e13e384086d5a242d52 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 20:52:35 2024 +0300 Rename WeChat Agent configuration file This makes it more clear that it belongs to the agent. Otherwise, `config.yaml` and `configure.yaml` make you wonder. commit ccca72f8d1e602f7c42f4bd552193afa153c9b9d Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 20:49:06 2024 +0300 Move WeChat agent configuration to a template commit a4047d94d8877b4095712dfc76ac3082a1edca28 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 20:47:17 2024 +0300 Mount WeChat config as readonly and instruct bridge to not update it commit bc0e89f345bf14bbdbfd574bb60d93918c2ac053 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 20:46:33 2024 +0300 Sync WeChat config with upstream Brings up-to-date with: https://github.com/duo/matrix-wechat/commits/0.2.4/example-config.yaml commit a46f5b9cbc8bf16042685a18c77d25a606bc8232 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 19:48:17 2024 +0300 Rename some files commit 3877679040cffc4ca6cccfa21a7335f8f796f06e Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 19:47:10 2024 +0300 Update WeChat logging config This brings it up-to-date with what mautrix-go uses. Otherwise, on startup we see: > Migrating legacy log config .. and it gets migrated to what we've done here. commit e3e95ab234651867c7a975a08455549b31db4172 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 19:43:37 2024 +0300 Make sure matrix-wechat-agent runs as 1000:1000 It needs to write stuff to `/home/user/.vnc`. `/home/user` is owned by `user:group` (`1000:1000`), so it cannot run any other way. Previously, if the `matrix` user was uid=1000 by chance, it would work, but that's pure luck. commit 4d5748ae9b84c81d6b48b0a41b790339d9ac4724 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 18:57:09 2024 +0300 Pin wechat and wechat-agent versions commit 40d40009f19ebceed4126146cbb510a2c95af671 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 18:53:58 2024 +0300 docker_image -> container_image for WeChat bridge commit cc33aff592541913070d13288d17b04ed6243176 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 18:00:25 2024 +0300 docker_src -> container_src in WeChat bridge commit 42e6ae9a6483c8ca6d53b8052058d41d90d93797 Author: Slavi Pantaleev <slavi@devture.com> Date: Mon Jun 3 17:54:24 2024 +0300 matrix_go_wechat_ -> matrix_wechat_ The bridge is written in Go, but does not include Go anywhere in its name. As such, it's mostly useless to use `matrix_go_wechat` as the prefix. commit d6662a69d1916d215d5184320c36d2ef73afd3e9 Author: Tobias Diez <code@tobiasdiez.de> Date: Mon Mar 25 10:55:16 2024 +0800 Add wechat bridge
2024-06-03 18:06:19 +00:00
- custom/matrix-bridge-wechat
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-bridge-mautrix-facebook
- custom/matrix-bridge-mautrix-twitter
- custom/matrix-bridge-mautrix-hangouts
- custom/matrix-bridge-mautrix-googlechat
- custom/matrix-bridge-mautrix-instagram
Add support for bridging to Facebook Messenger and Instagram via mautrix-meta Related to: https://github.com/mautrix/facebook/issues/332 Fixes: https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3138
2024-02-19 08:13:36 +00:00
- custom/matrix-bridge-mautrix-meta-messenger
- custom/matrix-bridge-mautrix-meta-instagram
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-bridge-mautrix-telegram
feat: add files for signalgo installation
2023-12-14 15:01:44 +00:00
- custom/matrix-bridge-mautrix-signal
Added Google Messager Bridge (#2794) * intial commit * changed * Reorderd * merge old changes * added changes to matrix_servers * Remove duplicate discord * Update main.yml * added google message to configuring-playbook.md * Changed docs to add new changes * Changed bug? * Removed problem j2 values * Rename a service files * change how password hash string * Changed port number * Change how the local part works * Revert "Merge pull request #8 from shreyasajj/wsproxy" This reverts commit bb1b8fc67ca39f63ca77e70077be99cb2b32c4de, reversing changes made to cce6ba5f9d74f89172488afc8b1ef124031de8c1. --------- Co-authored-by: Shreyas Ajjarapu <github.tzarina@aleeas.com>
2023-07-21 11:33:52 +00:00
- custom/matrix-bridge-mautrix-gmessages
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-bridge-mautrix-whatsapp
wsproxy for Android SMS (#2261) * Inital work, copeid from mautrix-amp PR * Some fixes leftover code copeid over from whatsapp * Got it to run and register * Fixed service issue with docker image * I now realize I need 2 roles wsproxy and imessage * Got someting working, still rough * Closer to working but still not working * reverting ports * Update main.yml * Add matrix-nginx-proxy config for mautrix-wsproxy * Changed * Add back file * fix for error hopefully * Changed the the way nginx was recieved * basically did not add anything ugh * Added some arguments * just trying stuff now * Ugh i messed up port number * Changed docs * Change dns config * changed generic secret key * Testing new nginx proxy * test * Fix linting errors * Add mautrix syncproxy to wsproxy for Android SMS * WIP * Move wsproxy to custom * Squashed commit of the following: commit 943189a9aa163f9fbcb795636b4cc0fd3c0d2877 Merge: 4a229d68 f5a09f30 Author: Slavi Pantaleev <slavi@devture.com> Date: Sun Nov 13 08:54:32 2022 +0200 Merge pull request #2259 from throny/patch-3 warn users about upgrading to pg15 when using borg commit 4a229d68700536491ee3bec611f62568dbe7c442 Merge: 9b326e08 c68def08 Author: Slavi Pantaleev <slavi@devture.com> Date: Sun Nov 13 08:53:13 2022 +0200 Merge pull request #2260 from etkecc/patch-117 Update ntfy 1.28.0 -> 1.29.0 commit f5a09f30b746f1c19dbec3b077f9d3a612ba15e7 Author: throny <m.throne12@gmail.com> Date: Sat Nov 12 23:48:57 2022 +0100 Update maintenance-postgres.md commit b12cdbd99d381acc587cef7b895cd3ac814a230c Author: throny <m.throne12@gmail.com> Date: Sat Nov 12 23:40:46 2022 +0100 Update maintenance-postgres.md commit c68def0809aa68cf8a7c0c70b1e3ddad39db105a Author: Aine <97398200+etkecc@users.noreply.github.com> Date: Sat Nov 12 22:01:31 2022 +0000 Update ntfy 1.28.0 -> 1.29.0 commit adbc09f152c390af8f272a0580a1810983ae592f Author: throny <m.throne12@gmail.com> Date: Sat Nov 12 11:20:43 2022 +0100 warn users about upgrading to pg15 when using borg * Fix linting errors * Cleanup after merge * Correct outdated variable names * Enable both Android and iMessage with wsproxy * Restructure wsproxy service defs and nginx config * Fix linter errors * Apply suggestions from code review Co-authored-by: Slavi Pantaleev <slavi@devture.com> * Fix comments for documentation, volumes and ports * Correct mount syntax * Complete network and traefik support for wsproxy * Remove wsproxy data_path * Fix wsproxy service definitions * Actually include syncproxy service * Remove wsproxy PathPrefix, it needs a subdomain There's no setting in the iMessage bridge that allows a path. Also don't bind port by default, wsproxy has no TLS. Syncproxy should never expose a port, it's only internal. --------- Co-authored-by: hanthor <jreilly112@gmail.com> Co-authored-by: Miguel Alatzar <miguel@natrx.io> Co-authored-by: Shreyas Ajjarapu <github.tzarina@aleeas.com> Co-authored-by: Slavi Pantaleev <slavi@devture.com>
2023-08-23 12:05:32 +00:00
- custom/matrix-bridge-mautrix-wsproxy
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-bridge-mautrix-discord
- custom/matrix-bridge-mautrix-slack
- custom/matrix-bridge-mx-puppet-discord
- custom/matrix-bridge-mx-puppet-groupme
- custom/matrix-bridge-mx-puppet-steam
- custom/matrix-bridge-mx-puppet-slack
- custom/matrix-bridge-mx-puppet-twitter
- custom/matrix-bridge-mx-puppet-instagram
- custom/matrix-bridge-sms
- custom/matrix-bridge-heisenbridge
- custom/matrix-bridge-hookshot
- custom/matrix-bot-matrix-reminder-bot
- custom/matrix-bot-matrix-registration-bot
- custom/matrix-bot-maubot
- custom/matrix-bot-buscarron
- custom/matrix-bot-honoroit
- custom/matrix-bot-postmoogle
- custom/matrix-bot-go-neb
- custom/matrix-bot-mjolnir
- custom/matrix-bot-draupnir
- custom/matrix-bot-chatgpt
- custom/matrix-cactus-comments
Add matrix-cactus-comments-client role This is split out from matrix-cactus-comments (see 241779b583a4730c), but also heavily inspired by `matrix-static-files`.
2024-01-09 07:53:01 +00:00
- custom/matrix-cactus-comments-client
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-rageshake
- custom/matrix-synapse
- custom/matrix-synapse-auto-compressor
- custom/matrix-synapse-reverse-proxy-companion
- custom/matrix-dendrite
- custom/matrix-conduit
- custom/matrix-synapse-admin
Created role for synapse-usage-exporter (#3442) * Created role for synapse-usage-exporter * Apply suggestions from code review Co-authored-by: Slavi Pantaleev <slavi@devture.com> * Renaming docker variables and moving synapse stats config location * Respect devture_systemd_docker_base_docker_service_name --------- Co-authored-by: Slavi Pantaleev <slavi@devture.com>
2024-07-25 17:19:08 +00:00
- custom/matrix-synapse-usage-exporter
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- galaxy/prometheus_node_exporter
- galaxy/prometheus_postgres_exporter
- custom/matrix-prometheus-nginxlog-exporter
- galaxy/prometheus
- galaxy/grafana
- custom/matrix-prometheus-services-connect
- custom/matrix-registration
- custom/matrix-client-element
- custom/matrix-client-hydrogen
- custom/matrix-client-cinny
schildichat fixes
2023-08-30 20:03:33 +00:00
- custom/matrix-client-schildichat
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- galaxy/jitsi
- custom/matrix-user-verification-service
- custom/matrix-ldap-registration-proxy
- custom/matrix-ma1sd
- custom/matrix-dimension
- galaxy/etherpad
- custom/matrix-sliding-sync
- custom/matrix-email2matrix
- custom/matrix-sygnal
- galaxy/ntfy
[WIP] Initial work on matrix-static-files role
2024-01-03 11:05:59 +00:00
- custom/matrix-static-files
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- custom/matrix-coturn
Added matrix-media-repo role
2023-07-12 06:09:27 +00:00
- custom/matrix-media-repo
Add Pantalaimon support This is actually authored by Julian Foad here (https://lab.trax.im/matrix/matrix-docker-ansible-deploy), but was in need of a rebase and various adjustments caused by huge playbook refactoring that landed in the past months. This rework is completely untested. Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/266
2024-03-24 16:25:19 +00:00
- custom/matrix-pantalaimon
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/postgres_backup
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- role: galaxy/backup_borg
- custom/matrix-user-creator
- custom/matrix-common-after
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/container_socket_proxy
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/traefik
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/traefik_certs_dumper
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
Make AUX role run last (before service manager role) Fixes https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/3292
2024-04-24 11:41:16 +00:00
- role: galaxy/auxiliary
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
- when: devture_systemd_service_manager_enabled | bool
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
role: galaxy/systemd_service_manager
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
# This is pretty much last, because we want it to better serve as a "last known good configuration".
# See: https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/2217#issuecomment-1301487601
- when: devture_playbook_state_preserver_enabled | bool
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
role: galaxy/playbook_state_preserver
Move playbooks to root directory (fixes #2513) Some time ago a "playbooks" subdirectory had been created and setup.yml had been moved there (as matrix.yml), together with the new jitsi_jvb.yml. However, jitsi_jvb.yml wouldn't work at all, unless a symbolic link to it was created from the root directory. A symbolic link setup.yml for playbooks/matrix.yml had already been created and committed. This seems to indicate that the developers thought they should place all playbooks in a subdirectory, but when this didn't work, they linked to one of them, leaving the other one inoperative. We fix this by moving the playbooks to the root directory. This works, and the pollution of the root directory is not too bad since it's only two playbooks. We also change the mode of setup.yml to 644 (it had inexplicably changed to 755 in 9735a2f600). This contribution is provided by GRNET S.A. (grnet.gr).
2023-06-05 14:28:05 +00:00
tags:
- setup-all
- install-all
Add explicit names for roles (affects their install paths)
2023-11-19 12:08:03 +00:00
- role: galaxy/playbook_runtime_messages
Reference in New Issue Copy Permalink