github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-22 06:02:06 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

[PR #1794] [MERGED] feat: add ability to configure a HTTP ChromaDB client #7580

New Issue
Closed
opened 2025-11-11 17:30:46 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 17:30:46 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/1794
Author: @cheahjs
Created: 4/27/2024
Status: ✅ Merged
Merged: 4/27/2024
Merged by: @tjbck

Base: dev ← Head: feat/external-chromadb

📝 Commits (1)

  • 8df7db1 feat: add ability to configure a HTTP ChromaDB client

📊 Changes

1 file changed (+30 additions, -4 deletions)

View changed files

📝 backend/config.py (+30 -4)

📄 Description

Pull Request Checklist

  • Description: Briefly describe the changes in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?

Description

Addresses the vector DB portion of https://github.com/open-webui/open-webui/issues/1397

Adds the following environment variables to configure a HTTP client for ChromaDB to connect to a ChromaDB Server instead of a local client:

  1. CHROMA_HTTP_HOST - Hostname to connect to
  2. CHROMA_HTTP_PORT - Port to connect to, defaults to 8000
  3. CHROMA_HTTP_HEADERS - Any headers to add to requests
  4. CHROMA_HTTP_SSL - Use TLS for connections

These additional env vars also apply to local ChromaDB:

  1. CHROMA_TENANT
  2. CHROMA_DATABASE

To test this locally,

  1. Start a ChromaDB server instance: docker run -p 8000:8000 --rm chromadb/chroma
  2. Configure the backend env vars: CHROMA_HTTP_HOST=localhost CHROMA_HTTP_PORT=8000 GLOBAL_LOG_LEVEL=DEBUG ./start.sh

Changelog Entry

Added

  • 🌐 Remote ChromaDB Support: Add the ability to connect to a remote ChromaDB server

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/1794 **Author:** [@cheahjs](https://github.com/cheahjs) **Created:** 4/27/2024 **Status:** ✅ Merged **Merged:** 4/27/2024 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `feat/external-chromadb` --- ### 📝 Commits (1) - [`8df7db1`](https://github.com/open-webui/open-webui/commit/8df7db1e17f6918dedff64939cbda4c6b6b118db) feat: add ability to configure a HTTP ChromaDB client ### 📊 Changes **1 file changed** (+30 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `backend/config.py` (+30 -4) </details> ### 📄 Description ## Pull Request Checklist - [x] **Description:** Briefly describe the changes in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? --- ## Description Addresses the vector DB portion of https://github.com/open-webui/open-webui/issues/1397 Adds the following environment variables to configure a HTTP client for ChromaDB to connect to a ChromaDB Server instead of a local client: 1. `CHROMA_HTTP_HOST` - Hostname to connect to 2. `CHROMA_HTTP_PORT` - Port to connect to, defaults to 8000 3. `CHROMA_HTTP_HEADERS` - Any headers to add to requests 4. `CHROMA_HTTP_SSL` - Use TLS for connections These additional env vars also apply to local ChromaDB: 1. `CHROMA_TENANT` 2. `CHROMA_DATABASE` To test this locally, 1. Start a ChromaDB server instance: `docker run -p 8000:8000 --rm chromadb/chroma` 2. Configure the backend env vars: `CHROMA_HTTP_HOST=localhost CHROMA_HTTP_PORT=8000 GLOBAL_LOG_LEVEL=DEBUG ./start.sh` --- ### Changelog Entry ### Added - 🌐 **Remote ChromaDB Support**: Add the ability to connect to a remote ChromaDB server --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-11 17:30:46 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#7580
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?