data.coop
/
ansible
8
3
Fork 7
Code Issues 44 Pull Requests 7 Projects 1 Releases Wiki Activity

Add uptime-kuma push url for restic #203

Merged
reynir merged 2 commits from restic-uptime-kuma into main 2024-03-06 12:29:45 +00:00
Conversation 2 Commits 2 Files Changed 5 +181 -165
reynir commented 2024-03-05 08:57:17 +00:00
Owner
Copy Link

I set up a push monitor in our uptime kuma and created a script for restic that calls the push monitor url on successful backup. I already deployed it.

I set up a push monitor in our uptime kuma and created a script for restic that calls the push monitor url on successful backup. I already deployed it.
reynir added 1 commit 2024-03-05 08:57:17 +00:00
reynir added 1 commit 2024-03-05 08:58:04 +00:00
reynir commented 2024-03-05 09:14:29 +00:00
Author
Owner
Copy Link

We can add a ?ping=XYZ parameter to the URL with the time it took to run the backup. Resticker has PRE_COMMANDS environment variable with commands to run before backup. The PRE_COMMANDS and POST_COMMANDS_* are run using eval (I know, right?!). So we can set up PRE_COMMANDS: "export RESTIC_UPTIME_KUMA_START=date +%d" and then in success.sh do calculations on how long it took to do the backup.

Probably we want to separate the url from the uptime kuma token in the ansible vault

We can add a `?ping=XYZ` parameter to the URL with the time it took to run the backup. Resticker has `PRE_COMMANDS` environment variable with commands to run before backup. The `PRE_COMMANDS` and `POST_COMMANDS_*` are run using [eval](https://github.com/djmaze/resticker/blob/553cd0db39260f47f85af40c280cebe07a52a1de/backup#L6) (I know, right?!). So we can set up `PRE_COMMANDS: "export RESTIC_UPTIME_KUMA_START=date +%d"` and then in `success.sh` do calculations on how long it took to do the backup. Probably we want to separate the url from the uptime kuma token in the ansible vault
reynir merged commit ebf3608bdc into main 2024-03-06 12:29:45 +00:00
reynir deleted branch restic-uptime-kuma 2024-03-06 12:29:45 +00:00
reynir commented 2024-03-06 12:30:14 +00:00
Author
Owner
Copy Link

I merged this as I already deployed it. There is definitely room for improvement, but we can defer that to another PR.

I merged this as I already deployed it. There is definitely room for improvement, but we can defer that to another PR.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
Blocked

Something is blocking progress

  
Existing Service

Issues/improvements regarding existing services

  
Infrastructure Issue

Infrastructure issue that needs investigation or time to fix

  
Refactor

Refactoring of files / file structure or other improvements

  
Security Hardening

Non-verified / non-critical security improvements

  
Security Issue

Urgent security issue that needs to be fixed ASAP

  
Service Idea

Ideas for new services

  
Service Removal

Removal of services for one reason or another

  
Upgrade service
No Label
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
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: data.coop/ansible#203
No description provided.
Delete Branch "restic-uptime-kuma"

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?