FR: Allow setting BORG_BASE_DIR.

[git70]

The problem

It is now possible to connect to an existing repository. But Borg backend config is always in /.var/app/com.borgbase.Vorta/config/borg I personally use Borg and Vorta for a variety of tasks I'm using a custom BORG_BASE_DIR location However, connecting to an existing repository does not allow you to use the same Vorta and Borg configuration (keys, security, nonces, etc)

Requested Solution

It seems that in addition to specifying the location of the existing repository, you can also specify the folder of the used Borg configuration. What do you think?

[m3nu]

That's a pure Flatpak issue due to sandboxing, right? Since ordinary installs would use those folders in default locations.

[git70]

That's a pure Flatpak issue due to sandboxing, right?

Hmm, maybe not, since Vorta flatpak has never (so far) reported me an access permission issue in my use case. Besides, the sandbox is probably adjustable at developer and user level via Flatseal.

Since ordinary installs would use those folders in default locations.

It is even more useful to be able to use a custom config folder (for regular installation and flatpak)

[real-yfprojects]

So how can Vorta tell borg to use a different config/cache/data location?

[git70]

Now in Vorta you can specify additional Shell Commands options for Borg in the Schedule tab (for example --read-special). Is it possible to add a new field for specifying arguments to be executed before the borg init, borg create, etc command in the terminal.

In my use case (using pure Borg) it is: sudo BORG_BASE_DIR='path' BORG_PASSCOMMAND='cat path' borg create...