I can't get this to install

[haydonryan]

Hi Three, I'm trying to setup an environment to sync a bunch of MDs to my vault.

$ deno install
✅ Granted import access to "github.com:443".
error: Module not found "https://github.com/vrtmrz/vrtmrz/trystero#9e892a93ec14eeb57ce806d272fbb7c3935256d8".

Also is it possible to exclude certain files / directories?

How does the filesync work? is it running a couchdb locally and then on the server too, then diff between them?

[vrtmrz]

Thank you for opening this issue!
I have been completely absorbed with my day job and the main repository, so I had not noticed.
I will fix this shortly!

P.S. Perhaps it would be better to move this repository to the main repository as well.

P.P.S. The forked Trystero is now merged to the upstream!

[haydonryan]

Thank you for the ultra fast reply!

I will admit i'm a little confused which repo to use. I am running a headless linux machine, that I want to have sychronize notes (for openclaw), to a folder in a vault.

https://github.com/vrtmrz/filesystem-livesync seemed to work, but did sychronize the .git folder that is also in there.
Which repository should I be using for that? This one?

( I see filesystem-livesync is EOL - would you consider setting it to archive?).

[sytone]

I am doing something similar in setting up a headless instance on my home server for backup and automation. Still have to look at openclaw. I have a PR that fixes this issue as well

[haydonryan]

I'm working on a vibe coded couchdb sync in rust. I have a working prototype,it does a on demand sync vs a proper live sync.

When i'm comfortable that it's a decent level of quality I'll be posting it to my github

[sytone]

@vrtmrz I notice that vrtmrz/livesync-commonlib moves pretty quickly, is there a better way to keep the headless version in sync and tested so you can choose the plugin version for this to work with or can we have a tagging and release process for the headless version so it is in sync with the release versions of the plugin? A github workflow may be able to help with this.

You can have a workflow get and update this repo, build and test it as part of the pr/release validation for the plugin and if passes it commits the update with the same tag

[sytone]

@vrtmrz could the common lib also just be published so it is an import and not a sub module which would make the management simpler as you can explicitly version and test common and then the plugin and the headless version are clear what version of the common library are being used from a release perspective.

[sytone]

@vrtmrz basically I want to have the equivalent capability with the stores as https://help.obsidian.md/sync/headless

[haydonryan]

Not sure if I should post this here - but will happily remove if @vrtmrz asks

https://github.com/haydonryan/couchdb-file-sync - I have those capabilities, plus telegram notifications for errors / sync.

[sytone]

@haydonryan this is using the encryption and model that the livesync process uses in the obsidian plugin?

[haydonryan]

it's direct into couchdb, vs direct to clients. It's super alpha though and live is something I do want to implement at some point. Currently I have it syncing openclaw into a folder of my obsidian vault (not syncing the whole vault).

[sytone]

ok, close to what I want but I want the live sync bridge to be a headless version of the plugin, jet need a way for the common library to be always in sync between the plugin and the headless instance here or some solution that provides that. @vrtmrz to comment on this.