snegov/cura-te-ipsum
1
0
Fork 0
Code Issues 29 Releases Wiki Activity

No notification system for backup failures #17

New Issue
Open
opened 2025-11-15 03:44:18 +00:00 by snegov · 0 comments
snegov commented 2025-11-15 03:44:18 +00:00
Owner
Copy Link

No notification system for backup failures

Priority: Medium
Component: cli.py, backup.py
Type: Feature

Description

If a backup fails (especially when run via cron), there's no mechanism to notify the user. Silent failures could lead to discovering weeks later that backups haven't been working.

Proposed Solution

Add optional notification support:

  1. Email notifications

    cura-te-ipsum -b /backups /data --notify-email user@example.com

  2. Webhook notifications

    cura-te-ipsum -b /backups /data --notify-webhook https://hooks.example.com/backup

  3. Log to syslog

    cura-te-ipsum -b /backups /data --syslog

  4. Integration with monitoring tools (healthchecks.io, UptimeRobot, etc.)

Could be configured in the config file (Issue #12).

Impact

Medium - Important for production/automated deployments.

# No notification system for backup failures **Priority:** Medium **Component:** cli.py, backup.py **Type:** Feature ## Description If a backup fails (especially when run via cron), there's no mechanism to notify the user. Silent failures could lead to discovering weeks later that backups haven't been working. ## Proposed Solution Add optional notification support: 1. **Email notifications** ```bash cura-te-ipsum -b /backups /data --notify-email user@example.com ``` 2. **Webhook notifications** ```bash cura-te-ipsum -b /backups /data --notify-webhook https://hooks.example.com/backup ``` 3. **Log to syslog** ```bash cura-te-ipsum -b /backups /data --syslog ``` 4. **Integration with monitoring tools** (healthchecks.io, UptimeRobot, etc.) Could be configured in the config file (Issue #12). ## Impact **Medium** - Important for production/automated deployments.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: snegov/cura-te-ipsum#17
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?