Ben Johnson

I was thinking about this some more. The `mount-dir` only makes sense in the context of FUSE and it won't be needed when this is used as a VFS. I...

@markuswustenberg I moved the `mount-dir` to `fuse.dir` in this PR: https://github.com/superfly/litefs/pull/239

@markuswustenberg I moved the `data-dir` and `retention` fields into a `data` section in this PR: https://github.com/superfly/litefs/pull/240

@patte I added a PR (https://github.com/superfly/docs/pull/1342) to document the WebSockets limitation. The tricky thing about supporting WebSockets is that messages don't have traditional HTTP verbs that indicate a read-only request...

@dastbe We're holding off on adding additional lease provider for the moment. One issue is that bundling in clients will may the `litefs` binary size explode. We've had requests for...

Yeah, Go's plugin system kinda sucks. :) I haven't seen Hashicorp's before but it seems a little complicated since it runs over gRPC. I'll keep it in mind though in...

@balchua LiteFS needs a concept of a leader since SQLite is single-writer. AFAICT, memberlist doesn't provide anything like leader election. It's mainly for eventually consistent gossip messaging.

I don't think I quite understand. You want to run the HTTP replication over a socket-activated Unix socket?

@nickchomey Yes, there are a few places that we could implement batching that would improve throughput. However, the biggest performance issue is going through FUSE. We have plans for implementing...

> I was under the impression that FUSE was chosen because it was more performant. The main reason for using FUSE was that folks could run on LiteFS without any...