Once you are done reading, please delete the above notes
Use case or problem
I run an always-on NAS that holds the master copy of my vault so other devices and automated scripts can read/write the live files without a desktop app running. The official obsidian-headless client (Feb 2026) does this via CLI, but ships only as an npm/Node tool. Installing Node 22 + npm on a locked-down NAS OS (Synology/QNAP), or depending on a third-party Docker image, is fragile and unsupported.
Proposed solution
Publish an official, multi-arch Docker image (and ideally a Synology/QNAP package) for obsidian-headless that runs ob sync --continuous as a supervised service, configured via env vars (auth token, vault path, sync mode). This gives NAS users first-class, supported headless sync without managing a Node runtime.
Current workaround (optional)
Master vault on the always-on NAS, synced by a community Docker image (Belphemur/crosbyh) that wraps the official CLI. Previously considered mirroring via Synology Drive as a second courier alongside Obsidian Sync, but that splits the vault across two sync systems and handles mobile poorly.
Related feature requests (optional)
- Possibility for headless syncing with a CLI/daemon (now implemented → Feature archive)
- Obsidian Sync: Self-Hosted Server (on premise)