Wedding Computer Sync

Two-way sync between an Obsidian vault and wedding.computer: your contacts, weddings, and checklists as plain markdown files, editable on desktop and mobile. No git required.

Wedding Computer/
├── contacts/
│   └── sarah-james.md
└── weddings/
    └── 2026-06-07-sarah-james/
        ├── wedding.md    ← details (frontmatter) + notes (body)
        ├── todo.md       ← checklist, tick boxes anywhere
        └── log.md        ← change log (read-only)

Edits you make in Obsidian appear in Wedding Computer seconds later, and changes from the app (or your couples) flow back into your vault.

Install

The plugin is in the official Obsidian community directory:

1. In Obsidian: Settings → Community plugins → Browse.
2. Search for Wedding Computer Sync, install, and enable it.

Or manually: download main.js and manifest.json from the latest release into <your vault>/.obsidian/plugins/wedding-computer-sync/, then reload Obsidian and enable the plugin.

Setup

1. In Wedding Computer: Settings → Device sync → Generate sync token (requires Pro).
2. In the plugin settings: paste the token, press Test — you should see your business name — then Sync.

The token is kept in device-local storage, never in the vault, so it can't leak through vault syncing (git, Obsidian Sync, iCloud). Enter it once per device.

How sync works

• The server is the source of truth; etags detect changes on both sides.
• Local edits push a couple of seconds after you stop typing; a full reconcile also runs on an interval (default: every minute).
• If both sides changed the same file, your local version is kept next to the file as <name>.conflict.md and the server version wins. Merge by hand, then delete the conflict copy.
• log.md is generated by the app and is read-only.
• Renaming or deleting files locally does not rename/delete in Wedding Computer — manage those in the app. (Deleted local files re-download.)
• New files need valid frontmatter (contacts/weddings require an id), so create new records in the app for now and edit them anywhere.

Development

npm install
npm run dev       # watch build
npm run build     # production build → main.js

Releases: tag the repo with the version number (e.g. 0.1.1, matching manifest.json) and the GitHub Action builds and attaches the release assets.

Wedding Computer itself is open source (AGPL-3.0): github.com/joshwithers/wedding-computer.

License

AGPL-3.0