From 572d2a4631ffd1b89da59c2459b0c98bf616c514 Mon Sep 17 00:00:00 2001 From: Catalan Lover Date: Sun, 3 May 2026 18:53:48 +0200 Subject: [PATCH] Add docs entry that talks about conditional restarts. --- docs/configuring-playbook-appservice-draupnir-for-all.md | 8 ++++++++ docs/configuring-playbook-bot-draupnir.md | 8 ++++++++ 2 files changed, 16 insertions(+) diff --git a/docs/configuring-playbook-appservice-draupnir-for-all.md b/docs/configuring-playbook-appservice-draupnir-for-all.md index 8827f759c..4743977eb 100644 --- a/docs/configuring-playbook-appservice-draupnir-for-all.md +++ b/docs/configuring-playbook-appservice-draupnir-for-all.md @@ -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. diff --git a/docs/configuring-playbook-bot-draupnir.md b/docs/configuring-playbook-bot-draupnir.md index 2175320b8..eeee41641 100644 --- a/docs/configuring-playbook-bot-draupnir.md +++ b/docs/configuring-playbook-bot-draupnir.md @@ -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.