From eed45f162785167107bfe03fb1d28d900f7ce399 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Kr=C3=BCger?= Date: Mon, 8 Jun 2026 22:30:40 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20update=20README=20=E2=80=94=20add=20not?= =?UTF-8?q?ifications=20section=20for=20n8n/Telegram?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-Authored-By: Claude Sonnet 4.6 --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md b/README.md index 16c16ad..ca73044 100644 --- a/README.md +++ b/README.md @@ -68,6 +68,16 @@ ssh vps 'systemctl status stacks-backup.timer' ssh vps 'source ~/stacks/_backup/.env && restic -r /mnt/hidrive/users/valknar/Backup/stacks snapshots' ``` +## Notifications + +Watchtower and the backup script both POST to an n8n webhook, which forwards messages to Telegram. + +The webhook URL is set in two places: +- `_backup/.env` → `WEBHOOK_URL` +- `watchtower/.env` → `NOTIFICATION_URL` (uses `generic+https://` shoutrrr scheme) + +Both point to the same n8n workflow at `https://n8n.pivoine.art`. The workflow accepts `{ "text": "..." }` (backup) and `{ "message": "..." }` (watchtower) and sends either field to Telegram. + ## Data Persistent data is stored in `~/stacks/.data//` on the VPS using bind mounts. Database stacks use dedicated Postgres instances with simple credentials.