From 791f6f3b69a36ad5fc6f8ed30ea43ebd50cd9cdb Mon Sep 17 00:00:00 2001 From: counterweight Date: Fri, 11 Sep 2026 21:56:13 +0200 Subject: [PATCH] ntfy: target monitoring group instead of watchtower Co-Authored-By: Claude Opus 5 (1M context) --- ansible/services/ntfy/deploy_ntfy_playbook.yml | 2 +- ansible/services/ntfy/setup_ntfy_uptime_kuma_notification.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/ansible/services/ntfy/deploy_ntfy_playbook.yml b/ansible/services/ntfy/deploy_ntfy_playbook.yml index 0729baa..d030123 100644 --- a/ansible/services/ntfy/deploy_ntfy_playbook.yml +++ b/ansible/services/ntfy/deploy_ntfy_playbook.yml @@ -1,5 +1,5 @@ - name: Deploy ntfy and configure Caddy reverse proxy - hosts: watchtower + hosts: monitoring become: yes vars_files: - ../../infra_vars.yml diff --git a/ansible/services/ntfy/setup_ntfy_uptime_kuma_notification.yml b/ansible/services/ntfy/setup_ntfy_uptime_kuma_notification.yml index 5ba03f1..8041905 100644 --- a/ansible/services/ntfy/setup_ntfy_uptime_kuma_notification.yml +++ b/ansible/services/ntfy/setup_ntfy_uptime_kuma_notification.yml @@ -1,5 +1,5 @@ - name: Setup ntfy as Uptime Kuma Notification Channel - hosts: watchtower + hosts: monitoring become: no vars_files: - ../../infra_vars.yml