From 1da1a425241104160c5c323b22ceac37e17a035b Mon Sep 17 00:00:00 2001
From: kenpat <kenpat7177@gmail.com>
Date: Mon, 15 Jun 2026 16:07:21 -0500
Subject: [PATCH] Document Kuma ntfy notifications

---
 project-kitestacks-migration.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/project-kitestacks-migration.md b/project-kitestacks-migration.md
index f463067..4ec596e 100644
--- a/project-kitestacks-migration.md
+++ b/project-kitestacks-migration.md
@@ -880,3 +880,25 @@ See [[project-per-scholas-capstone]]. Next steps:
 - Create capstone incident tickets in osTicket (5-phase challenge)
 - Set up osTicket user/client portal for non-staff users (Phase 3 end-user access)
 - Each capstone ticket maps to a phase scenario (migration event, incident response, etc.)
+
+## 2026-06-15: Uptime Kuma -> ntfy phone notifications configured
+
+- ntfy is running at `https://ntfy.kitestacks.com` with deny-by-default auth.
+- Existing ntfy user `alerts` has write-only access to all topics and now has a
+  dedicated access token for Uptime Kuma. Do not write the token into repo/memory.
+- Phone subscription topic: `kitestacks-uptime-VHr1DMQNi8`.
+- Anonymous/everyone access is read-only for that single topic, so phones can
+  subscribe without needing the Kuma publish token.
+- Uptime Kuma notification row:
+  - name `KiteStacks ntfy`
+  - type `ntfy`
+  - server URL `http://ntfy` on the shared Docker network
+  - topic `kitestacks-uptime-VHr1DMQNi8`
+  - auth method `accessToken`
+  - active/default, linked to active monitors `T14 Deb Assassin` and `Google DNS`
+- Verified by sending a Kuma-provider test message and reading it publicly via
+  `https://ntfy.kitestacks.com/kitestacks-uptime-VHr1DMQNi8/json?poll=1`.
+- To add to a phone home screen: open
+  `https://ntfy.kitestacks.com/kitestacks-uptime-VHr1DMQNi8` on the phone, allow
+  notifications, then use the browser share/menu action to add ntfy to the home
+  screen.