concept of backups - Githubissues

pandrr commented 1 month ago

current backup functionality is quite useless when using subpatch ops

propsal/idea:

when creating an export internally a "patch export" will be done and saved. on load we will import this into a new(/temporary) patch

steam0r commented 3 days ago

[ ] remove "backups" in menu
[ ] create backup -> save patch-export patch ("all") without showing options to zip in bucket
[ ] still use database entries and logic for backup rotation
[ ] patreon feature, owner of patch has to be patreon, also user that saves has to be patreon
[ ] announce that old backups will not be around in six month to come, when that's the case
[ ] limit backups by userlevel and size, autobackup feature
[ ] somehow find workflow that is close to current
[ ] backup before export then is also on bucket
[ ] later maybe offer import that does not create patchops from everything
[ ] add download and "create patch from backup" buttons to overview of backups
[ ] show percentage usage of backup space to user on overview
[ ] tell user that these are rolling backups
[ ] delete oldest backup when out of space for new backup
[ ] tell user that offsite backups are a good idea

pandrr commented 3 days ago

tdb limits:

1gb - 0.005 euro copper? 10gb - 0.05 euro bronze? 100gb - 0.5 euro silver?

steam0r commented 3 days ago

cables-gl / cables