goebbe

@m3nu Right now, this is too difficult for me. :-( There are too many concepts in the programme-code that are new to me, and I currently don't have the time...

@mplorentz The easiest workaround is: After setting/ changing the schedule, run the backup manually, once. At the moment, "run missed backups" relies on the timing of the "last_run" backup. Edit:...

+1 The advantage of flatpak is that it is easy to install the package on many distributions. By the way: Linux Mint supports flatpak out of the box. Here is...

If something like a Edit repository dialog will be implemented another possible field could be the "Repository Name" In Vorta 9.1., I didn't find a way to edit/ change the...

Related: https://github.com/borgbase/vorta/issues/1918

In the current version of Vorta it is easy to export the settings on a per-profile base. Doing this, the users are asked if the repo passphrase should be included...

I just tested the behaviour, using Vorta 9.1. - When creating a new repo using Vorta, there is **no hint** for a "borg key backup". - Currently there is no...

@ThomasWaldmann exactly. I tried to test if **Vorta** passes the information/ warning about the keys to the user. If I understand correctly, users should be encouraged to make a backup...

@ThomasWaldmann `borg key export ` could be used in both cases (i.e. when using a (local) keyfile OR when using repokey) - so Vorta could use this command anyway. In...

Related: https://github.com/borgbase/vorta/pull/599 from @samu-w