Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT]: The ability to route saved conversations to a scalable storage database #2583

Closed
danielrosehill opened this issue Nov 4, 2024 · 1 comment
Labels
enhancement New feature or request feature request

Comments

@danielrosehill
Copy link

What would you like to see?

I'd love to be able to store conversations in a custom endpoint.

This might allow the conversation history to be mined and explored in parallel systems like wikis / knowledge management tools.

For this to work effectively, individual outputs would need to be batched into their constituent conversations.

Logical databases for storage might be Postgres or MongoDB.

@danielrosehill danielrosehill added enhancement New feature or request feature request labels Nov 4, 2024
@timothycarambat
Copy link
Member

I'd love to be able to store conversations in a custom endpoint.

Could you not export the information from the API endpoint /v1/system/export-chats and upload to your db of choice?

As far as other databases go, this is capture in #2574

The reason for SQLite is it is zero config or set up and the docker setup flows down into the desktop app via the desktop branch it is critical we don't ask people installing a desktop app "Okay, now first set up a PostgreSQL db" - which is a nonstarter for that userbase.

There are some subtle differences between SQLite/PG, but they prisma schemas should be able to port for the most part

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request feature request
Projects
None yet
Development

No branches or pull requests

2 participants