✨ Feat(backend/vector): chromadb client-server support#285
Merged
Conversation
MasterKenth
force-pushed
the
feat/chromadb-client-server
branch
from
aa463e9 to
f253fba
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added support for connecting to a server instance of chromadb (as an alternative to "running" it locally which is the pre-existing behavior).
To enable, set the environment variable
CHROMADB_HOSTto the hostname, and optionallyCHROMADB_PORTto a port value if using something other than the default (8000).To test or run a ChromaDB server, follow https://docs.trychroma.com/docs/cli/install. The sample command used during development to test was
chroma run --path ./__chromadb_server --port 8003.