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

docs/draupnir: polish "running both modes" sections

Browse Source 
Sentence-case the heading to match the rest of the file, fix a broken
"appservice mode](url)(Draupnir for all)" link by folding the
parenthetical into the link text, hyphenate "non-release tag" and
"force-restart", correct "a update" -> "an update", and reword "work
perfectly" to the more accurate "work correctly".

Follow-up to 75f097e55 (#5187).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Slavi Pantaleev
2026-05-04 16:18:21 +03:00
parent 75f097e55c
commit b51881c90a
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/configuring-playbook-appservice-draupnir-for-all.md
+5 -5
View File
@@ -48,13 +48,13 @@ 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
### 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.
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 a development build.
This is due to the conditional restart logic not being able to reliably tell when an update happened.
Conditional restarts work perfectly for all tags when running only one of these two operating modes.
Conditional restarts work correctly for all tags when running only one of these two operating modes.
### Extending the configuration
docs/configuring-playbook-bot-draupnir.md
+5 -5
View File
@@ -82,13 +82,13 @@ matrix_bot_draupnir_login_native: true
matrix_bot_draupnir_config_managementRoom: "MANAGEMENT_ROOM_ID_HERE"
```
### Running Both Bot Mode and Appservice Mode
### 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.
When running both bot mode and [appservice mode (Draupnir for all)](./configuring-playbook-appservice-draupnir-for-all.md), the
playbook will force-restart the bot if running a non-release tag like `latest` or `main` or a development build.
This is due to the conditional restart logic not being able to reliably tell when an update happened.
Conditional restarts work perfectly for all tags when running only one of these two operating modes.
Conditional restarts work correctly for all tags when running only one of these two operating modes.
### Create and invite the bot to the management room