docs: update README — add notifications section for n8n/Telegram
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -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'
|
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
|
## Data
|
||||||
|
|
||||||
Persistent data is stored in `~/stacks/.data/<stack>/` on the VPS using bind mounts. Database stacks use dedicated Postgres instances with simple credentials.
|
Persistent data is stored in `~/stacks/.data/<stack>/` on the VPS using bind mounts. Database stacks use dedicated Postgres instances with simple credentials.
|
||||||
|
|||||||
Reference in New Issue
Block a user