Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remote borg client #53

Closed
ThomasWaldmann opened this issue Nov 24, 2018 · 3 comments
Closed

remote borg client #53

ThomasWaldmann opened this issue Nov 24, 2018 · 3 comments
Labels
status:planning For large features, plan it out before implementation type:feature New functionality

Comments

@ThomasWaldmann
Copy link
Collaborator

for the use case of e.g. backing up a local server and still wanting a nice gui, vorta could invoke ssh user@server borg ... instead of just borg ....

problem: all places using the file/directory selector dialog from the local OS / FS.

@ThomasWaldmann
Copy link
Collaborator Author

using vorta on the server would be an alternative to above. ssh -X or x2go.

@m3nu m3nu added type:feature New functionality status:planning For large features, plan it out before implementation labels Nov 27, 2018
@arthurlutz
Copy link

This could also mean generating borg commands that are setup remotely on the server so that a cron can handle the borg commands instead of being launched by vorta (or is this kind of feature a separate issue?)

@ThomasWaldmann
Copy link
Collaborator Author

@arthurlutz sound like a slightly different idea.

Also, generating commands for cron makes no difference whether you'ld edit these commands into your local or remote crontab. But I fear this is slightly out-of-scope of vorta anyway (and people who deal with crontabs and servers maybe don't need vorta to create the right commands anyway).

@m3nu m3nu closed this as completed Feb 15, 2021
@borgbase borgbase locked and limited conversation to collaborators Feb 15, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
status:planning For large features, plan it out before implementation type:feature New functionality
Projects
None yet
Development

No branches or pull requests

3 participants