sync-minecontext

Syncing MineContext data to Obsidian requires querying the MineContext SQLite database and writing daily reports, activity logs, tips, and todos as markdown files into corresponding Obsidian vault folders. This enables centralized knowledge management.

The MineContext to Obsidian sync uses idempotent markdown file writing, ensuring existing notes are not duplicated or overwritten unnecessarily. This keeps your Obsidian vault structure clean and safe during repeat incremental syncs.

Organizing MineContext daily reports in Obsidian is best handled by mapping each data type to a specific dedicated folder. The sync workflow automatically directs daily reports, activity logs, tips, and todos into separate directories for structured access.

Incremental sync for Obsidian activity logs works by querying the MineContext SQLite database and writing only the updated entries. It processes data by date or item, ensuring new activity logs are visible and traceable without reprocessing the entire database.

Syncing MineContext with Obsidian requires configuring the local MineContext SQLite database path and the target Obsidian vault folders. Once these paths are set, the Python-based workflow can safely query and write data.

MineContext todos may not appear in Obsidian if the target Obsidian vault directories are not created or the database path is incorrect. The sync workflow handles directory creation automatically, but correct path configuration is required.