-
Notifications
You must be signed in to change notification settings - Fork 1
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
Server-side configuration #1
Comments
Thanks for opening this issue! I would propose the following: After a library is available (which already started in rustic-rs/rustic#617) I would make a real client/server application where on the server side the clients configuration and scheduling is managed. The client could then be simply a daemon registering at the server and obtaining the data currently available in the config file directly from the server and then simply call the rustic library to do the backup - and afterwards telling the server about being successful. Related to rustic-rs/rustic#171 I would be very happy if you can contribute or even start such an application but I can also support you in your work! |
@dionorgua I wrote a proof-of-concept client/server backup scheduler which should go in the direction you are seeking, see https://github.com/rustic-rs/rustic_scheduler. I'll move this issue over there... |
@dionorgua I would be very happy if you could try out the present very beta version. Even more if you could add feedback (issues) on what might be good extensions to rustic_scheduler... |
Hi,
I'm trying to migrate from
restic
torustic
and get some benefits of config files.There are tons of wrappers around
restic
. I'm personally using my own that also stores configuration on remote side. And I want to get rid of it :)So I want to propose some discussion about this feature. What I would like to have is:
self-update
if needed using my own build (basically tested/approved build)Ideally I would like to just add
rustic poll-do-geverything
to/etc/cron.hourly
and let it do everything needed (basically just check and do backup if needed).cron.hourly
is used here to make sure backup is retried in case of network failure.Right now I've custom wrapper for restic and I'm using
rest-server
as backend for this. Just extrarestic
-like repo is hijacked and reused to serve this. But I think we can think about extra directory layout.PS. Most likely I'll try to contribute code if it's interesting
The text was updated successfully, but these errors were encountered: