Skip to content
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

make it possible to "serve" a borg repository #26

Open
wnhre2ur8cxx8 opened this issue Oct 19, 2021 · 5 comments
Open

make it possible to "serve" a borg repository #26

wnhre2ur8cxx8 opened this issue Oct 19, 2021 · 5 comments

Comments

@wnhre2ur8cxx8
Copy link

I thought this was the point of the plugin, but I dont see a way how to do it.

It would be nice to have some way to make the repository accessible for other clients so they can backup to my NAS.

@wnhre2ur8cxx8
Copy link
Author

Maybe a way to do it would be to add "borg --serve" or something as a possible shell to choose when creating a user?

@ryecoaaron
Copy link
Member

The plugin was designed to backup content on the omv system to a local or remote borg repo. You could create a repo and backup from a client to that repo via ssh.

I’ve never used borg serve even though I do backup to remote borg repos. Looking at the borg docs, borg serve still uses ssh. I guess I will have to read more to see what that is actually providing.

@NovaViper
Copy link

So, the plugin isn't designed to host a borg repo?

@ryecoaaron
Copy link
Member

Yes, it is hosting a borg repo. It was designed to backup content on the OMV server to additional locations on the OMV or
to a remote server with borg installed. It just isn’t running a “server”. You can still create archives in a repo created by the plugin via ssh. Borg uses ssh even if running a “server”. I have looked at the borg serve command but I still don’t understand how using it would be any different.

@wnhre2ur8cxx8
Copy link
Author

It is basically a security feature. A command you add to your "authorized-keys" file so clients that backup to your server are not allowed to do anything else than connecting to the borg repo. I was a bit unsure on how the workflow of OMV works when I created the issue. But basically I thought it would be nice to have a possibility in the gui to add a repo thats purpose is to be accesible via ssh for a seperate user. So that would include choosing a user that owns the repo, adding a public key to authoriz and adding the borg serve command correctly in the authorized-keys file. Maybe thats a bit overkill for the extension, since most of the stuff is added to the user. I dont know how extensions are supoosed to modify the system and if this is in the scope of the extension.

Thing is, that I was not really able to add the needed configs in the gui, especcially the restriced authorized-keys stuff. So maybe think about if this is possible and worth it :) thanks anyway for working on this extension!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants