Open kuyagic opened 3 years ago
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.
@wojas what is the difference between this approach over rclone serve restic --append-only
?
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.
How to handle retention if rclone serve restic
with --append-only
is used?
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.
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 arestic forget
cronjob against the second rclone.
restic forget rclone:~~~
is more simple way i think
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