Can’t sync to VPS when it’s set up (blocks FR-025)
Risk of data loss if the local machine fails
Can’t use Obsidian mobile as a capture tool
Proposed Solution
Choose a sync method and set it up early so all future work is sync-ready.
Options to Evaluate:
Option
Pros
Cons
Obsidian Sync
Official, conflict resolution, selective sync
Paid ($4/mo), only Obsidian
Git push/pull
Free, already have GitHub
Not real-time, merge conflicts, binary files
Syncthing
Free, real-time, peer-to-peer
Needs setup on each device, no central server
OneDrive / Google Drive
Free tier, automatic
Conflict issues with Obsidian, can corrupt vault
Open Questions
1. Sync Method
Question: Which sync method to use?
Option
Description
A) Obsidian Sync
Official, best conflict resolution, $4/mo
B) Git push/pull
Free, already set up, not real-time
C) Syncthing
Free, real-time, more setup
D) Cloud Drive
Free, automatic, conflict risk
Recommendation: For phone, Obsidian Sync or Syncthing are likely best. Git on phone is painful.
Decision: Git-based sync via Obsidian Git plugin. Free, works with existing GitHub repo. Quartz web viewer for read-only browsing. See vault/00_system/mobile-sync-guide.md.
Phase Overview
Phase
Description
Status
Phase 1
Decide on approach + set up for Opus vault
—
Phase 2
Extend to Atlas vault + VPS
—
Phase 1: Decision & Setup —
Goal: Evaluate options, choose a sync method, and set it up for the Opus vault.
File / Feature
Details
Owner
Status
Evaluate options
Test top 2 candidates with Opus vault
mv
done
Choose approach
Git-based sync via Obsidian Git plugin
mv
done
Set up sync
Follow vault/00_system/mobile-sync-guide.md
mv
—
Test on phone
Verify vault is readable in Obsidian mobile
mv
—
Document setup
vault/00_system/mobile-sync-guide.md created
opus
done
Phase 2: Extend —
Goal: Apply sync to the Atlas vault and VPS.
File / Feature
Details
Owner
Status
Atlas vault sync
Apply same strategy to personal vault
mv
—
VPS sync
Ensure vault syncs to VPS (pairs with FR-025)
opus
—
Conflict resolution
Document how to handle sync conflicts
opus
—
Prerequisites / Gap Analysis
Requirements
Requirement
Description
REQ-1
FR-025 (VPS) — for Phase 2 sync to server
REQ-2
Obsidian mobile installed on phone
Current State
Component
Status
Details
Git repo
done
FR-028 completed, GitHub remote set up
Obsidian desktop
done
Vault open locally
Obsidian mobile
—
Not yet set up
Gap (What’s missing?)
Gap
Effort
Blocker?
Sync method decision
Low
Yes (blocks everything)
Sync configuration
Med
No
Phone setup
Low
No
Test
Manual tests
Test
Expected
Owner
Actual
Last
Opus vault accessible on phone
Vault opens in Obsidian mobile
mv
pending
-
Desktop changes appear on phone
Sync within reasonable time
mv
pending
-
Sync method documented
Setup guide in vault
opus
pending
-
No data loss from sync
Files intact after sync cycle
mv
pending
-
AI-verified tests
Scenario
Expected behavior
Verification method
…
…
…
E2E tests
Scenario
Assertion
…
…
Integration tests
Component
Coverage
…
…
Unit tests
Component
Tests
Coverage
…
…
…
History
Date
Event
Details
2026-02-27
Promoted from idea
From vault/10_features/01_ideas/vault-sync-strategy.md
2026-02-27
Renumbered
From FR-023 to FR-020
2026-02-28
Reformatted
Aligned to feature-request template
2026-03-20
Decision made
Git-based sync chosen, mobile guide written, Quartz web viewer set up
References
FR-025 (VPS Deployment) — Phase 2 sync to server
FR-032 (Phone Access) — benefits from vault on phone
FR-028 (GitHub Integration) — git-based sync has low friction since git is already set up