y-sweet

Author here — I think our own almost server is almost exactly what you’re looking for? Y-Sweet [1] is open source, written in Rust and persists documents to S3. We offer a hosted version if you want to quickly check it out, which you can use with your own S3 bucket if you want to self host eventually. This is the first I’ve heard of Platejs, but we do have a tutorial on integrating a block editor using BlockNote [2] [1] https://github.com/jamsocket/y-sweet [2] https://docs.jamsocket.com/y-sweet/tutorials/blocknote

Y-sweet (which this is built with) allows you to make a Yjs app local-first by passing “offlineSupport” to the provider when constructing. There’s a demo of this here: https://demos.y-sweet.dev/color-grid The source for that demo is here: https://github.com/jamsocket/y-sweet/blob/5fa6941cf5568f4a3f... That demo uses react, but there is a vanilla js version of the same demo here: https://github.com/jamsocket/y-sweet/tree/main/examples/vani... (The vanilla js version is not local first, but it would just be a matter of passing the same offlineSupport flag to make it so.)

You might like Y-Sweet[1], an open-source Rust server that powers the banner on Learn Yjs. It uses S3 or the local filesystem for storage, and it compiles down to a musl-linked binary that weighs a few megabytes. https://github.com/jamsocket/y-sweet

Great write-up! > If we extend it further with a fairly simple distributed mutex mechanism, we can now persist and share state across any service which can access the Redis instance! I’m curious to hear more about the approach you took here. Does the first server to open the document hold the mutex, or do servers only hold the mutex when briefly while they persist data? (I’ll also shamelessly plug Y-Sweet, an open source Yjs server with persistence that I contribute to https://github.com/jamsocket/y-sweet)

For the specific example of a Yjs backend, I happen to be working on one that can be hosted either on Cloudflare or as a native process. We’ve had people running in production migrate from cloudflare to native just by swapping out the URL they connect to in their application config. https://github.com/jamsocket/y-sweet

I’m biased as one of the authors of Y-Sweet, but I think Jake’s choice of Yjs + Y-Sweet is as good as any to start with. We’ve worked a lot at making the localhost environment easy to get started with, and Yjs is the de facto CRDT with the most written about it. https://github.com/jamsocket/y-sweet

Direct link to ticket: https://github.com/drifting-in-space/y-sweet/issues/78

I used Algora for an issue for an open source project (y-sweet[1]) after bashing my head against the wall for 30 mins on it. It ended up being one of those “knowing where to hit the hammer” type problems and someone solved it in a matter of minutes with a 1 LOC PR. Money well spent. [1] https://github.com/drifting-in-space/y-sweet/

> knowing for sure what state a user’s client is in when debugging is tough too My team has built an open-source debugger for Yjs that might interest you (docs: https://y-sweet.cloud/advanced/debugger) You mention the investor-funded services that pop up to make this stuff easier -- our goal with Y-Sweet is to build the same type of DX you’d get from those services, but build it on a fully open-source (MIT) platform with Yjs at the core: https://github.com/drifting-in-space/y-sweet