From 0528be517f9a1234208b0c1f8afc8e99b7cb3fb0 Mon Sep 17 00:00:00 2001 From: Zandre Engelbrecht Date: Mon, 11 Nov 2024 09:37:46 +0200 Subject: [PATCH] small doc changes --- changelog/0084-add-geospatial-queue.yml | 7 +++++-- docs/source/changelog/0084-add-geospatial-queue.md | 7 +++++-- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/changelog/0084-add-geospatial-queue.yml b/changelog/0084-add-geospatial-queue.yml index 9c9bf7345a..27b9084f61 100644 --- a/changelog/0084-add-geospatial-queue.yml +++ b/changelog/0084-add-geospatial-queue.yml @@ -18,10 +18,13 @@ update_steps: | This update should be performed before updating CommCare to a version more recent than that specified above. First, add a queue called `geospatial_queue` to your app_processes.yml, - following the examples in commcare-cloud commit a94636b1d. + following the examples in commcare-cloud commit [a94636b1d](https://github.com/dimagi/commcare-cloud/commit/a94636b1d). - To apply this change, run: + Then, to apply this change: ``` commcare-cloud update-supervisor-confs ``` + + Please note that a restart is required for the change to take effect and can be done as part of the above command + or with a separately done deploy. diff --git a/docs/source/changelog/0084-add-geospatial-queue.md b/docs/source/changelog/0084-add-geospatial-queue.md index 73d07f5041..6002aed59a 100644 --- a/docs/source/changelog/0084-add-geospatial-queue.md +++ b/docs/source/changelog/0084-add-geospatial-queue.md @@ -26,10 +26,13 @@ Microplanning feature. This update should be performed before updating CommCare to a version more recent than that specified above. First, add a queue called `geospatial_queue` to your app_processes.yml, -following the examples in commcare-cloud commit a94636b1d. +following the examples in commcare-cloud commit [a94636b1d](https://github.com/dimagi/commcare-cloud/commit/a94636b1d). -To apply this change, run: +Then, to apply this change: ``` commcare-cloud update-supervisor-confs ``` + +Please note that a restart is required for the change to take effect and can be done as part of the above command +or with a separately done deploy.