From fcf412b13b2700b54a828e4bbf5b7039e6d9aa41 Mon Sep 17 00:00:00 2001
From: Slawomir Koszewski <slawek@koszewscy.waw.pl>
Date: Thu, 21 May 2026 17:47:30 +0200
Subject: [PATCH] Correction related to the Azure Function deployment.

---
 README.md | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 368d069..a94c89c 100644
--- a/README.md
+++ b/README.md
@@ -181,7 +181,7 @@ az role assignment create \
   --scope /subscriptions/<subscription-id>/resourceGroups/<dns-resource-group>
 ```
 
-**6. Configure application settings**
+**6. Configure production application settings**
 
 ```sh
 az functionapp config appsettings set \
@@ -191,19 +191,22 @@ az functionapp config appsettings set \
     "ACME_KEYVAULT_URL=https://<keyvault-name>.vault.azure.net" \
     "ACME_SUBSCRIPTION_ID=<subscription-id>" \
     "ACME_RESOURCE_GROUPS=<dns-resource-group>" \
-    "ACME_CONTACT_EMAIL=<email>"
+    "ACME_CONTACT_EMAIL=<email>" \
+    "ACME_SCHEDULE=0 0 2 * * *"
 ```
 
 **7. Build and deploy**
 
 ```sh
 npm run build
-func azure functionapp publish <function-app-name>
+func azure functionapp publish <function-app-name> --no-build
 ```
 
+`--no-build` tells `func` to skip its own build step since we already compiled the TypeScript output. To also push application settings from `local.settings.json` in the same step, append `--publish-local-settings --overwrite-settings`. This is useful for the initial deployment or when settings and code change together.
+
 ### Local testing
 
-Create a `local.settings.json` file at the project root (it is gitignored):
+Create `local.settings.json` at the project root (gitignored) and fill in your values:
 
 ```json
 {