per-worker ntfy topics for targeted push notifications
Evelin receives all booking notifications via the shared ntfy topic in config. Each worker also gets notified on their own personal ntfy topic (set per-worker in the admin panel) — so workers only see their own booking events. - _ntfy() now accepts optional $workerTopic and sends to both topics if different - All three call sites (new/modify/cancel) pass $worker->ntfy_topic - Admin worker form + worker_process() wired for ntfy_topic field - DB: ALTER TABLE workers ADD COLUMN ntfy_topic VARCHAR(100) NULL DEFAULT NULL Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -56,6 +56,10 @@
|
||||
<label class="formTitle">Google Calendar ID</label>
|
||||
<input type="text" class="formInputBox" name="google_calendar_id" value="<?php echo isset($selectedItem->google_calendar_id) ? $selectedItem->google_calendar_id : '';?>">
|
||||
</div>
|
||||
<div class="formRow">
|
||||
<label class="formTitle">ntfy Topic</label>
|
||||
<input type="text" class="formInputBox" name="ntfy_topic" value="<?php echo isset($selectedItem->ntfy_topic) ? $selectedItem->ntfy_topic : '';?>">
|
||||
</div>
|
||||
<div class="formRow">
|
||||
<input type="submit" class="submitButton" name="updateWorker" value="Módosítás">
|
||||
<a href="<?php echo base_url();?>workers" class="cancelButton">Mégsem</a>
|
||||
|
||||
Reference in New Issue
Block a user