The source forum post is an introduction and external tutorial link rather than a complete deployment record. It promises a quick CasaOS setup for Obsidian Self-hosted LiveSync, but the post itself does not preserve the CouchDB image, volume paths, credentials, HTTPS configuration, or client setup used in the original video.
For a current installation, use the maintained Self-hosted LiveSync project as the technical baseline. The upstream setup still centers on CouchDB and explicitly documents Docker, persistent CouchDB data/configuration, HTTPS exposure, and a setup URI for configuring Obsidian clients.
Self-hosted LiveSync Is a Sync Layer, Not the Obsidian App Itself
Obsidian remains installed on your desktop or mobile devices. Self-hosted LiveSync adds a community synchronization plugin plus a server-side database so vault changes can move among devices without relying on Obsidian's paid Sync service.
The upstream project is community software, not an official Obsidian service.
CouchDB Is the Core Server Component
The current upstream setup guide uses CouchDB as the primary self-hosted backend. Its Docker example creates persistent directories for both CouchDB data and configuration before starting the container.
Use the current Self-hosted LiveSync server setup instead of copying old image tags from a video.
Persist the CouchDB Database Outside the Disposable Container
The database contains the synchronized representation of your notes and related state. Map CouchDB's data and configuration directories to persistent CasaOS storage so recreating the container does not erase the sync backend.
Keep those folders separate from ordinary temporary Docker layers.
Use Unique CouchDB Credentials
Do not keep sample usernames or passwords from a tutorial. Create strong unique CouchDB administrator credentials and keep them out of screenshots, shared Compose files, and public forum posts.
If credentials are exposed, rotate them and review any remotely reachable CouchDB instance immediately.
Remote Sync Should Use HTTPS
If multiple devices need to sync outside the LAN, expose CouchDB through a secure HTTPS path rather than publishing plain HTTP directly to the Internet. The upstream documentation includes reverse-proxy examples and domain configuration.
A VPN/overlay network is another option when only your own devices need access.
CORS and Origin Settings Must Match the Client Workflow
CouchDB security configuration can block browser/webview requests even when the server is reachable. Self-hosted LiveSync's setup procedure configures the required CouchDB behavior rather than treating a generic database container as finished after port 5984 opens.
Use the Setup URI Carefully
Current upstream guidance can generate a setup URI so another Obsidian device can import connection settings. That URI can contain sensitive connection details.
Treat it like a secret: send it only to your own trusted device and avoid posting it in screenshots or chat history that other people can access.
Real-Time Sync Does Not Eliminate Editing Conflicts
Two devices editing the same note at nearly the same time can still create conflicts or require reconciliation. Self-hosting gives you control over the server; it does not turn distributed editing into a single-writer filesystem.
Test the workflow with a disposable vault before migrating your only copy of important notes.
Sync Is Not a Backup
If a note is deleted and that deletion syncs to every client, the synchronized system has done its job. Keep independent versioned backups of the Obsidian vault and, when appropriate, the CouchDB data.
This protects against accidental deletion, plugin bugs, database corruption, or a mistaken bulk edit.
The Source Is CasaOS-Specific
The historical tutorial targeted CasaOS. If the host is now ZimaOS, use the current ZimaOS App Store/Compose workflow and current storage paths rather than assuming the same CasaOS package layout.
Obsidian LiveSync FAQ
Does the original forum post contain the full Compose configuration?
No. It primarily links to the external Big Bear tutorial.
What backend does current Self-hosted LiveSync document?
The current upstream setup uses CouchDB and provides a Docker deployment path.
Does self-hosted sync replace backups?
No. Keep an independent backup of the vault because deletions and bad edits can synchronize too.
