apunkt/SurfSense
1
0
Fork 0
mirror of https://github.com/MODSetter/SurfSense.git synced 2026-04-29 10:56:24 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

feat: implement sync notifications for Obsidian plugin

Browse source 
- Added functionality to create and update notifications during the Obsidian sync process.
- Improved handling of sync completion and failure notifications.
- Updated connector naming convention in various locations for consistency.
This commit is contained in:
Anish Sarkar 2026-04-22 06:38:51 +05:30
parent 3b7f27cff9
commit 4a75603d4f
4 changed files with 134 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

4
surfsense_web/content/docs/connectors/obsidian.mdx
View file

@ -30,7 +30,7 @@ This works for cloud and self-hosted deployments, including desktop and mobile c
4. Paste your SurfSense API token from the user settings section.
5. Paste your Server URL in the plugin setting: either your SurfSense main domain (if `/api/v1` rewrites are enabled) or your direct backend URL.
6. Choose the Search Space in the plugin, then the first sync should run automatically.
7. Confirm the connector appears as **Obsidian — <vault>** in SurfSense.
7. Confirm the connector appears as **Obsidian - <vault>** in SurfSense.
## Migrating from the legacy connector
@ -38,7 +38,7 @@ If you previously used the legacy Obsidian connector architecture, migrate to th
1. Delete the old legacy Obsidian connector from SurfSense.
2. Install and configure the SurfSense Obsidian plugin using the quick start above.
3. Run the first plugin sync and verify the new **Obsidian — <vault>** connector is active.
3. Run the first plugin sync and verify the new **Obsidian - <vault>** connector is active.
<Callout type="warn">
Deleting the legacy connector also deletes all documents that were indexed by that connector. Always finish and verify plugin sync before deleting the old connector.