Building a self-hostable sync implementation

Sorry to just be continuously pinging this thread, but one big update: As of this morning, I think the OSS Logseq Sync backend has everything it needs to be actually usable. The last remaining piece was persistence, which I submitted this morning.

The next step is to engage with the Logseq team for the stuff that needs to change on the Logseq client side of things, which is mainly just adding additional configuration settings in the (advanced) settings. I’m happy to make these changes, but I want some sort of confirmation they’ll be accepted before I start learning ClojureScript and Rum.

Aside from that, there’s also a parallel discussion about protocol-level changes we could have. For example, right now it’s tightly coupled to AWS + S3, and I haven’t touched anything regarding AWS Cognito integration yet (meaning you still need a Logseq account to use self-hosted sync).

What’s the appropriate forum for this discussion? Is it here, or GitHub Issues/Discussions, or somewhere else? Happy to engage with the team wherever makes sense.

3 Likes