960 B
960 B
TODO
- Write README
restic backup
can take a long time: stream output to logging somehow to keep track of what it's doing.- Make Restictray non-dependent on existing config in
~/.restic
:- Create default files if not existing?
- Create a config dialog in https://developer.fyne.io/
- Add additional resilience:
- What if SSH backup and network goes down? Do a
ping
before backup? Is there a timeout from therestic
command itself? - If something goes wrong, menu shows error and app becomes unusable. Perhaps not all errors (e.g. above one) have to be this way.
- Is backing up while mounted ok? => yes
restic backup
can result inWarning: at least one source file could not be read\n: exit status 3
. This returns an error, but the backup itself seems to be all right.- Verify backups with
restic check
? If not okay, remove (snapshot/folder?) and rebackup? What's the plan then?
- What if SSH backup and network goes down? Do a