More Drives

[michaelquigley]

Features to be incorporated into the next major round of drives functionality.

• S3 storage
• More robust synchronization
• More robust end-user implementation

[michaelquigley]

Investigate JuiceFS:

https://juicefs.com/

[qrkourier]

It would be helpful if zrok drive could additionally handle GET requests. That way, I could share an HTTP link to the files in my zrok drive the same way I do for the zrok web backend, and the same files would still be available in the file explorer/manager/finder app.

[qrkourier]

I was privately asked for help with drives because it's unclear from the drives doc in https://docs.zrok.io/docs/guides/drives/cli/ (or blog posts) that a zrok drive is not a web site, and visiting the drive in a web browser will get the error "method not allowed" (GET).

The user was confused because they expected to see the drive contents at the private proxy URL provided by zrok access private {drive share token}.

Supporting GET for drives would soften the user experience somewhat, but there also seems to be a need to clarify how accessing a WebDAV drive is different from accessing a website. If we add more types of drives, then we'll at least need a hint about where to get info for each permutation supported drive type (file-like protocol, e.g., WebDAV, S3, etc.) and major OS, e.g., macOS Finder can use WebDAV directly, but may need Cyberduck to use S3.