Replies: 7 comments
-
Sure. We had long discussions on which archive name to use. Now that was all in vain... :-) |
Beta Was this translation helpful? Give feedback.
-
not in vain, it can be used as the default value still. when making this adjustable, there needs to be also flexible prune prefix and maybe some sanity check, so people do not accidentally prune away lots of stuff. |
Beta Was this translation helpful? Give feedback.
-
Here what I got so far. There is a preview and it won't save unless the formatting works. Still thinking about the sanity check to avoid excessive pruning.. |
Beta Was this translation helpful? Give feedback.
-
Left to do:
|
Beta Was this translation helpful? Give feedback.
-
For borg cli, the sanity check is by the user reading the output of |
Beta Was this translation helpful? Give feedback.
-
I ended up moving those 2 options to the Archives tab and putting the other pruning options in a separate section. Made more sense to keep them together. I'd also prefer to set new archive names per-profile instead of globally. Will merge this as 0.6.1 (pre-release) soon, since there are 2 other bugs I'd like to see corrected. If you can think of any changes to improve this feature, let me know. |
Beta Was this translation helpful? Give feedback.
-
Screenshot of new Prune Options section. Left to do:
|
Beta Was this translation helpful? Give feedback.
-
It would be great to be able to specify your own templates for archive names, just like when using borg backup from the CLI. For example:
$ borg create /path/to/repo::{hostname}-{user}-{now} ~
.$ borg create /path/to/repo::{hostname}-{user}-{now:%Y-%m-%dT%H:%M:%S.%f} ~
Beta Was this translation helpful? Give feedback.
All reactions