librclone for remote support

[darthShadow]

Just wondering if you would consider using librclone as a shim to allow usage of all remotes that rclone supports.

References:

https://docs.rs/librclone/latest/librclone/
https://github.com/rclone/rclone/tree/master/librclone

[m3nu]

What do you need in addition to S3? I started out with opendal but the dependencies were massive, so went to simpler integrations. And most places run S3 now, no?

[darthShadow]

Hi,

Thanks for checking.

At minimum a union type remote, because I like to have a hot backup split across multiple Hetzner Storage Boxes using SFTP. They only support pre-defined sizes and nothing dynamic so it's easier to union multiple of those and scale up as needed rather than paying upfront for unused storage.

Another nice-to-have would be Google Drive, again for hot backup.

Most (if not all) providers have very pricy S3 retrieval costs, so I like to use S3 providers only as cold backups.

[NeurekaSoftware]

I personally prefer using S3 whenever possible, but I do see the value in supporting rclone remotes. The reason being is that it opens up a LOT of backends very easily. Be it Proton Drive, an SSH remote (Hetzner Storage Boxes), or any other remote the user desires. Being able to union is also really nice.

That said, stability will always be the most important aspect of a backup solution. If you think that supporting rclone will add a lot of maintenance overhead or cause more edge cases- I would respect the decision to defer supporting rclone.