Obsidian Headless and Obsidian CLI are two separate things. CLI requires running the full app, and lets you do anything Obsidian can do. Headless doesn't require the app but for now it is just a Sync client.
- Markdown files: Obsidian Sync merges the changes using Google's diff-match-patch algorithm.
- Other file types: For all other files, including canvases, Obsidian uses a "last modified wins" approach. The most recently modified version replaces earlier versions.
For conflicts in Obsidian settings, such as plugin settings, Obsidian Sync merges the JSON files. It applies keys from the local JSON on top of the remote JSON.
Are there plans to support scoped token permissions (specific folders or even specific notes)? I'd love to try setting up something that automatically updates a specific Obsidian note on a state change or cronjob, but I'd want to avoid giving access to the rest of the vault.
also, thanks for the great product, bought the vip catalyst as a show of support.
Related tangent: "Relay" (https://relay.md") lets you sync / share files based on directory (vs. the whole vault). That enables things like "my private vault contains a subdir for work, and my work machine syncs to only that child subdir".
Thanks for your support! Sync is end-to-end encrypted so the server doesn't know about specific paths in your vault. You would have to set those permissions at the filesystem level, or with the tool you're using.
If your team is more technical Git is an option. If you want completely control over permissions and configuration then a shared drive is probably better.
No question. Just wanted to drop by and say Obsidian is actually pretty cool. An absolute joy to use, and I only wish I learned about it earlier than I did.
I’m using a couchdb instance to sync a bunch of local obsidian installs and use an obsidian plugin to keep them synced- would this change that or make it easier?
Thank you for making Obsidian! I am wondering if you have any plans to package the headless sync client up for container use in Docker or Podman?
Also, is the Obsidian CLI available when obsidian-headless is installed? Or is obsidian-headless only a sync client at this time?
Obsidian Headless and Obsidian CLI are two separate things. CLI requires running the full app, and lets you do anything Obsidian can do. Headless doesn't require the app but for now it is just a Sync client.
https://help.obsidian.md/headless
https://help.obsidian.md/cli
Wanted to say thanks. We were literally talking about the lack of a cli sync at work last week and I had moved to Syncthing because of that gap.
Definitely will be looking at the official Obsidian sync plan now.
How are sync conflicts handled in the filesystem? Say I write to a file and another client's edit wins and mine is rejected.
The headless Obsidian Sync client works the same way as desktop and mobile clients, see:
https://help.obsidian.md/sync/troubleshoot
- Markdown files: Obsidian Sync merges the changes using Google's diff-match-patch algorithm.
- Other file types: For all other files, including canvases, Obsidian uses a "last modified wins" approach. The most recently modified version replaces earlier versions.
For conflicts in Obsidian settings, such as plugin settings, Obsidian Sync merges the JSON files. It applies keys from the local JSON on top of the remote JSON.
Are there plans to support scoped token permissions (specific folders or even specific notes)? I'd love to try setting up something that automatically updates a specific Obsidian note on a state change or cronjob, but I'd want to avoid giving access to the rest of the vault.
also, thanks for the great product, bought the vip catalyst as a show of support.
Related tangent: "Relay" (https://relay.md") lets you sync / share files based on directory (vs. the whole vault). That enables things like "my private vault contains a subdir for work, and my work machine syncs to only that child subdir".
Thanks for your support! Sync is end-to-end encrypted so the server doesn't know about specific paths in your vault. You would have to set those permissions at the filesystem level, or with the tool you're using.
Do you have a good starting point or explanation to share about using obsidian for a team, where we all change/sync files?
Depends on the size of the team and your requirements. The Obsidian team uses a shared Sync vault, which works well for us:
https://help.obsidian.md/teams/sync
If your team is more technical Git is an option. If you want completely control over permissions and configuration then a shared drive is probably better.
https://help.obsidian.md/teams/deploy
No question. Just wanted to drop by and say Obsidian is actually pretty cool. An absolute joy to use, and I only wish I learned about it earlier than I did.
It would be nice if one could sync dot files in the vault. For example, the .claude or .pi folder containing skills and whatnot.
Yes, we're looking into that!
I’m using a couchdb instance to sync a bunch of local obsidian installs and use an obsidian plugin to keep them synced- would this change that or make it easier?
No questions, just thanks for helping with a great product.