Any non UI options to import profiles?

[hrafnthor]

Hi,

I'm trying to figure out if Vorta allows for a non UI method to import profile json data?

I know about issue #462 which mentions taking a backup of the whole settings.db. However, for setups that use git for tracking of changes storing a binary database is less than ideal.

Does Vorta have a CLI option to import a json profile? Or can the json profile be dropped in some folder where Vorta will read it on startup?

[goebbe]

The docs state the following about the use of a .json profile:

• it has to be placed in the users home directory ~
• has to be named .vorta-init.json
• this file will be imported automatically when starting (or restarting) Vorta
• this .json file will be deleted after import.

So, to my knowledge, the only non UI option (e.g. via shell script) is to:

• move / rename a .json file appropriately
• restart Vorta

Restarting Vorta (GUI) from a shell script can be pretty "interesting" since some environment variables have to be set appropriately. E.g. on Ubuntu, when using crontab to start Vorta I use the following command:
env DISPLAY=:0 env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus /bin/bash -c '/path/to/vorta &!'
Explanation:
DISPLAY is required, since Vorta is a GUI-App
DBUS_SESSION_BUS_ADDRESS is required to provide access to the passwords

Closing Vorta should be much easier, e.g. via pkill vorta

Hope this helps. Don't hesitate to share your experience, here.

[hrafnthor]

Thank you for the answer @goebbe, I had completely missed this. For others interested here is a direct link to the documentation.

It must be said though that this is an interesting implementation choice, as Vorta allows for multiple profiles to be used at once but this feature only supports importing a single one. But having this option is better than having none, I suppose.