Run commands from the CLI (single app)

borgbase / vorta

Desktop Backup Client for Borg Backup

https://vorta.borgbase.com

GNU General Public License v3.0

1.98k stars 130 forks source link

Run commands from the CLI (single app) #364

Closed asitemade4u closed 3 years ago

asitemade4u commented 4 years ago

As a data scientist, I get a lot of intermediate result files, generally CSVs. I would like to save these results from the code, besides the regular schedule of backups in the Vorta backup.

It would be practical (ifit does not already exist!) to be able to launch a backup defined in Vorta as a script from the Command Line (in my case Ubuntu/bash)

Launching from the Ubuntu Vorta menu is OK, but I often forget to do so whereas with a script called from the code I am working on, I would never forget...

asitemade4u commented 4 years ago

Another solution (but still unsatisfactory to me) would be to be able backup schedules with shorter span of time.

Hofer-Julian commented 4 years ago

Someone already opened an issue for that, which was closed quite immediately (https://github.com/borgbase/vorta/issues/293).

I see potential use cases for this feature as well, but at the same time it would make Vorta harder to maintain. I am unsure if the trade-off is worth it.

The only GUI I know which offers an extensive CLI is inkscape (http://tavmjong.free.fr/INKSCAPE/MANUAL/html/CommandLine-Export.html).

Hofer-Julian commented 4 years ago

As a data scientist, I get a lot of intermediate result files, generally CSVs. I would like to save these results from the code, besides the regular schedule of backups in the Vorta backup.

It would be practical (ifit does not already exist!) to be able to launch a backup defined in Vorta as a script from the Command Line (in my case Ubuntu/bash)

Launching from the Ubuntu Vorta menu is OK, but I often forget to do so whereas with a script called from the code I am working on, I would never forget...

What is the reason you don't use borg(matic)?

asitemade4u commented 4 years ago

I understand your point. However, would it be possible to add this feature:

one defines a backup script in Vorta as usual
a button allows to extract the substance of the backup script, as an interpreter would do, to a CLI script on disk
that way, the script on disk could be executed at will while being close to the Vorta backup script -- until it is next modified, of course.

Thanks again for Vorta, which is amazing when used locally as well as with a remote server

asitemade4u commented 4 years ago

I have been using borgbackup through the CLI for years now. I have tried BorgMatic, but did not find it such a compelling reason to switch to a semi-interpreter -- until I discovered Vorta, which makes it so much simpler to run unattended backups, besides several outstanding capabilities (mounting an archive)...

Hofer-Julian commented 4 years ago

I understand your point. However, would it be possible to add this feature:
* one defines a backup script in Vorta as usual

* a button allows to **extract** the substance of the backup script, as an interpreter would do, to a CLI script on disk

* that way, the script on disk could be executed at will while being close to the Vorta backup script -- until it is next modified, of course.
Thanks again for Vorta, which is amazing when used locally as well as with a remote server

This would probably complement the feature discussed here https://github.com/borgbase/vorta/issues/107. You are welcome to give the arguments a thumb up you agree to

samuel-w commented 4 years ago

Do we only need to implement backup creation? If so we can do something along the lines of vorta create --profile-name=Default and just call create_backup_action. Anything else can be done by the GUI, otherwise that defeats the point of Vorta.