jvilk / BrowserFS

BrowserFS is an in-browser filesystem that emulates the Node JS filesystem API and supports storing and retrieving files from various backends.
Other
3.07k stars 217 forks source link

Websocket Support #173

Closed svenefftinge closed 7 years ago

svenefftinge commented 7 years ago

We are looking for a solution that allows for using fs from a browser, connecting to a remote node server's fs. Is that already possible with BrowserFS or do we need another backend?

From what I understood the webworker implementation comes close.

jvilk commented 7 years ago

Someone else recently asked this question, so I pose the same questions to you.

jvilk commented 7 years ago

To answer your other question, BrowserFS provides read-only access to a file system over HTTP GETs, but assumes that the files are static (e.g., the files on the server do not change) and requires you to generate an index of those files.

jvilk commented 7 years ago

Oh, and if the second bullet is what you want, you'd need to write a new backend for that purpose. It should be relatively straightforward if you have poked at TypeScript code before, and there are existing tests you can run your file system against (just make a factory!). :)

svenefftinge commented 7 years ago

Thanks, for the answer. Yes, of course there are security concerns but it can be solved in different ways and doesn't necessarily need to be a responsibility of the BrowserFS backend. In my context, we spawn individual docker images in a private cloud. Those servers don't run long and are only accessible through a proxy. But I understood that you don't see this in the core framework, which is ok of course. I just wanted to make sure I don't miss something.