iartamonov/matrix-docker-ansible-deploy
1
0
Fork 0
mirror of https://github.com/spantaleev/matrix-docker-ansible-deploy.git synced 2026-05-11 14:40:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Modernise Draupnir Role ansible modules and update restart logic (#5187)

Browse Source
This commit is contained in:
Catalan Lover
2026-05-04 15:15:18 +02:00
committed by GitHub
parent c0ba02c83f
commit 75f097e55c
8 changed files with 70 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuring-playbook-appservice-draupnir-for-all.md
+8
View File
@@ -48,6 +48,14 @@ matrix_appservice_draupnir_for_all_enabled: true
matrix_appservice_draupnir_for_all_config_adminRoom: "MANAGEMENT_ROOM_ALIAS_HERE"
```
### Running Both Bot Mode and Appservice Mode
When running both [Bot mode](./configuring-playbook-bot-draupnir.md) and appservice mode the playbook will force restart
the bot if running a non release tag like `latest` or `main` or development builds.
This is due to the conditional restart logic not being able to tell when a update happened correctly.
Conditional restarts work perfectly for all tags when running only one of these two operating modes.
### Extending the configuration
There are some additional things you may wish to configure about the component.
docs/configuring-playbook-bot-draupnir.md
+8
View File
@@ -82,6 +82,14 @@ matrix_bot_draupnir_login_native: true
matrix_bot_draupnir_config_managementRoom: "MANAGEMENT_ROOM_ID_HERE"
```
### Running Both Bot Mode and Appservice Mode
When running both Bot mode and [appservice mode](./configuring-playbook-appservice-draupnir-for-all.md)(Draupnir for all) the
playbook will force restart the bot if running a non release tag like `latest` or `main` or development builds.
This is due to the conditional restart logic not being able to tell when a update happened correctly.
Conditional restarts work perfectly for all tags when running only one of these two operating modes.
### Create and invite the bot to the management room
Before proceeding to the next step, run the playbook with the following command to create the bot user.