coop-cloud/backup-bot-two
7
0
Fork 4
Code Issues 13 Pull Requests 1 Packages Projects Releases Wiki Activity

Manual backups don't send notifications #67

New Issue
Closed
opened 2024-11-08 13:13:58 +00:00 by fauno · 4 comments
fauno commented 2024-11-08 13:13:58 +00:00
Owner
Copy Link

It'd be great to test they're working too!

It'd be great to test they're working too!
moritz commented 2025-04-23 18:51:22 +00:00
Owner
Copy Link

You can use the run_cron command f7f46d7b7b/README.md (usage)
this will send a notification as well.
At the moment the notifications are built into the cronjob, this way a failure Notification can also be send, if the main program is crashing.

You can use the `run_cron` command https://git.coopcloud.tech/coop-cloud/backup-bot-two/src/commit/f7f46d7b7bc350aa8f46261be070fd2e14bc6ea1/README.md#usage this will send a notification as well. At the moment the notifications are built into the cronjob, this way a failure Notification can also be send, if the main program is crashing.
fauno commented 2025-04-23 19:14:40 +00:00
Author
Owner
Copy Link

so abra app cmd <backupbot_name> app run_cron is the same as abra app run <backupbot_name> app -- backup create plus notifications?

so `abra app cmd <backupbot_name> app run_cron` is the same as `abra app run <backupbot_name> app -- backup create` plus notifications?
fauno commented 2025-04-23 19:16:59 +00:00
Author
Owner
Copy Link

it seems so! though i got the ssh timeout error, even with abra 0.10 :/

it seems so! though i got the ssh timeout error, even with abra 0.10 :/
fauno closed this issue 2025-04-23 19:16:59 +00:00
decentral1se commented 2025-04-24 06:34:52 +00:00
Owner
Copy Link

i got the ssh timeout error

@fauno FWIW this should now only be related to your SSH client/server configurations and not abra as we do not hardcode any timeout in abra any more. If you manage to figure out how to resolve this via the SSH config, I'd love to hear about it / document it.

> i got the ssh timeout error @fauno FWIW this should now only be related to your SSH client/server configurations and not `abra` as we do not hardcode any timeout in `abra` any more. If you manage to figure out how to resolve this via the SSH config, I'd love to hear about it / document it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud cyrnel decentral1se fauno flancian Frando iexos jade javielico jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moritz nicksellen notplants p4u1 pau pharaohgraphy renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val virtualboys wolcen wykwit xynosis yksflip
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/backup-bot-two#67
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?