FR: Allow specifying BORG_CACHE_DIR

[mpr1255]

trafficstars

Description

This does not have an "error" message, but I definitely consider this a bug.

I am backing up a bunch of stuff and my cache has come to be 150gb. On a Mac Mini with 500gb SSD this is far too big. It's all stored on the system disk with no option to store the cache elsewhere.

Suggestion: Vorta needs to expose the option to change the cache location.

This would basically solve the problem I think.

Reproduction

• [X] I tried to reproduce the issue.
• [X] I was able to reproduce the issue.

OS

Mac OSX Monterrey

Version of Vorta

0.8.10

What did you install Vorta with?

Homebrew

Version of Borg

No response

Logs

No response

[real-yfprojects]

Did you already report this problem at their repo? While moving the cache location would be a solution, one should also consider preventing the cache from getting this big.

Vorta needs to expose the option to change the cache location.

How can this be done with borg?

[mpr1255]

I don't consider it a problem with borg itself. I'm backing up many TB of data, so a cache of 150gb might not be too crazy.

There are two possible flags for this in the reference:

BORG_BASE_DIR or BORG_CACHE_DIR, explained here: https://borgbackup.readthedocs.io/en/stable/usage/general.html

I mean the simplest general purpose solution is just to expose to the user a json with the borg commands that Vorta generates, and allow that file to be manipulated by the user. That way you don't have to trick out the GUI to a crazy degree to have every flag. If the user corrupts the file then just regen the defaults and make a new one. This is how a bunch of software handles things like this -- thinking of sumatrapdf for example.

[real-yfprojects]

I see. This issue is similar and linked to #1748.