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

use s3 like backend exclude rest-server like restic client #165

Open
kuyagic opened this issue Sep 7, 2021 · 6 comments
Open

use s3 like backend exclude rest-server like restic client #165

kuyagic opened this issue Sep 7, 2021 · 6 comments

Comments

@kuyagic
Copy link

kuyagic commented Sep 7, 2021

Use s3 like backend exclude rest-server like restic client will make rest-server a bridge between client and the backend with append-only support and user isolated repo

@wojas
Copy link
Contributor

wojas commented Sep 7, 2021

This is a duplicate of #39. That issue was closed, but I would actually be interested in reopening it. It would probably not be too hard to add pluggable filesystem backends with the new Repo abstraction.

@Enrico204
Copy link
Contributor

@wojas what is the difference between this approach over rclone serve restic --append-only?

@wojas
Copy link
Contributor

wojas commented Sep 9, 2021

Ah, looks like rclone server restic is pretty feature complete.

With the current feature set there is no strong case for a rest-server S3 backend then. This might change in the future as we add new features to rest-server.

@engel75
Copy link

engel75 commented Jan 21, 2022

How to handle retention if rclone serve restic with --append-only is used?

@Raboo
Copy link

Raboo commented Apr 21, 2022

Kind of ugly but I would setup a second rclone serve restic without the --append-only maybe an endpoint that listens to loopback only and then you have a restic forget cronjob against the second rclone.

@tribela
Copy link

tribela commented Aug 19, 2022

Kind of ugly but I would setup a second rclone serve restic without the --append-only maybe an endpoint that listens to loopback only and then you have a restic forget cronjob against the second rclone.

restic forget rclone:~~~ is more simple way i think

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

No branches or pull requests

6 participants