taproot-manufacturing/communal-compute
2
0
Code Issues 3 Projects Packages Wiki Activity Actions

improve resiliency #3

New issue
Open
opened 2025-06-18 00:10:58 -06:00 by sigil-03 · 1 comment
sigil-03 commented 2025-06-18 00:10:58 -06:00
Owner
Copy link

what steps can we take to improve the resiliency of the communal compute resources?

i.e.
distributed compute
backups + distribution of backups
failovers

what steps can we take to improve the resiliency of the communal compute resources? i.e. distributed compute backups + distribution of backups failovers
sigil-03 added this to the communal compute project 2025-06-18 00:10:58 -06:00
seb commented 2025-07-05 21:48:08 -06:00
Owner
Copy link

For backups i've been running this for years: https://github.com/sebKuzminsky/rsync-push-backup

For backups i've been running this for years: https://github.com/sebKuzminsky/rsync-push-backup
❤️ 1
sigil-03 changed title from improve resiliancy to improve resiliency 2025-07-05 22:26:21 -06:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
communal compute
Assignees
Clear assignees
No assignees
2 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: taproot-manufacturing/communal-compute#3
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?