apunkt/SurfSense
1
0
Fork 0
mirror of https://github.com/MODSetter/SurfSense.git synced 2026-06-02 19:55:18 +02:00
Code Issues Projects Releases Packages Wiki Activity

refactor(database): update default source values to 'surfsense' for chat threads and messages

Browse source
This commit is contained in:
Anish Sarkar 2026-05-28 13:11:05 +05:30
parent c958fe5bc6
commit 3faaa25af6
4 changed files with 11 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

2
surfsense_web/content/docs/manual-installation.mdx
View file

@ -41,7 +41,7 @@ The backend is the core of SurfSense. Follow these steps to set it up:
### Optional: Telegram External Chat Surface
SurfSense can expose the same canonical chat agent through Telegram. The `external_chat_*` tables store adapter identity, delivery configuration, and durable inbox rows. The actual chat thread and messages remain in `new_chat_threads` and `new_chat_messages`, and all chat-message sources are eligible for Zero replication so a future SurfSense UI layer can render external chat surfaces. The web app initially shows pairing, health, revoke, and resume controls under **User Settings > Messaging Channels**.
SurfSense can expose the same canonical chat agent through Telegram. The `external_chat_*` tables store adapter identity, delivery configuration, and durable inbox rows. The actual chat thread and messages remain in `new_chat_threads` and `new_chat_messages`, with first-party web/desktop chats marked as `source="surfsense"` and external surfaces marked by platform, such as `source="telegram"`. All chat-message sources are eligible for Zero replication so a future SurfSense UI layer can render external chat surfaces. The web app initially shows pairing, health, revoke, and resume controls under **User Settings > Messaging Channels**.
Add these variables to `surfsense_backend/.env` when enabling the Telegram surface: