Arthur Erlich haylan
haylan pushed to main at haylan/LLM-Server 2026-09-02 20:28:33 +00:00
b4dc83949e feat(litellm): add Redis for router state/rate-limits/budgets/cache
haylan pushed to main at haylan/LLM-Server 2026-09-02 20:21:57 +00:00
b996b1fe88 fix(scripts): update.sh now appends vars missing from .env, not just blank ones
haylan pushed to main at haylan/LLM-Server 2026-09-02 20:18:18 +00:00
24d749b2e0 feat(scripts): fold generate-secrets.sh into update.sh, auto-mint virtual keys
haylan commented on issue haylan/LLM-Server#24 2026-09-02 20:10:03 +00:00
Verify search + knowledgebase wiring (#21) on the real R9700 box

Updated scope after #25: this ticket now verifies memory-retrieval (the langchain_postgres.PGVector-based service, services/memory-retrieval/) instead of the retired litellm-pgvector

haylan closed issue haylan/LLM-Server#25 2026-09-02 20:09:50 +00:00
LangChain+pgvector direct RAG vs. the litellm-pgvector connector — which fits this stack?
haylan commented on issue haylan/LLM-Server#25 2026-09-02 20:09:49 +00:00
LangChain+pgvector direct RAG vs. the litellm-pgvector connector — which fits this stack?

Implemented — switched from litellm-pgvector to a LangChain-direct service (services/memory-retrieval/), per this ticket's verdict. Details in the commit on main (abeadc4): new `memory-retriev…

haylan pushed to main at haylan/LLM-Server 2026-09-02 20:09:39 +00:00
abeadc49c8 feat(knowledgebase): replace litellm-pgvector connector with memory-retrieval
e2a79eab4a docs(research): LangChain+pgvector-direct vs litellm-pgvector for issue #25
Compare 2 commits »
haylan commented on issue haylan/LLM-Server#25 2026-09-02 20:03:18 +00:00
LangChain+pgvector direct RAG vs. the litellm-pgvector connector — which fits this stack?

Verdict: switch to LangChain-direct. Full research + a concrete replacement-service spec: docs/research/langchain-pgvector-vs-litellm-pgvector.md on branch `research/langchain-pgvector-vs-lit…

haylan created branch research/langchain-pgvector-vs-litellm-pgvector in haylan/LLM-Server 2026-09-02 20:03:16 +00:00
e2a79eab4a docs(research): LangChain+pgvector-direct vs litellm-pgvector for issue #25
haylan opened issue haylan/LLM-Server#25 2026-09-02 19:55:46 +00:00
LangChain+pgvector direct RAG vs. the litellm-pgvector connector — which fits this stack?
haylan pushed to main at haylan/LLM-Server 2026-09-02 19:50:52 +00:00
7247674a9f fix(litellm-pgvector): vendor the source instead of a remote git build context
haylan pushed to main at haylan/LLM-Server 2026-09-02 19:44:33 +00:00
b0e37b2f4c chore(scripts): add update.sh, hook it into agent/deploy workflow
haylan closed issue haylan/LLM-Server#23 2026-09-02 19:39:30 +00:00
How does LiteLLM's knowledgebase/vector-store feature work, and what does it need?
haylan pushed to main at haylan/LLM-Server 2026-09-02 19:38:40 +00:00
f508f5670a feat(litellm): wire SearXNG search, pgvector knowledgebase, and memory ingestion
a3ecbc0e02 docs(research): investigate LiteLLM knowledgebase/vector_store feature for #23
8c42f2518b research: LiteLLM web-search + SearXNG wiring (issue #22)
Compare 3 commits »
haylan closed issue haylan/LLM-Server#22 2026-09-02 19:38:40 +00:00
How does LiteLLM's SearXNG web-search integration work, and what does wiring it in require?
haylan opened issue haylan/LLM-Server#24 2026-09-02 19:37:44 +00:00
Verify search + knowledgebase wiring (#21) on the real R9700 box
haylan commented on issue haylan/LLM-Server#23 2026-09-02 19:27:36 +00:00
How does LiteLLM's knowledgebase/vector-store feature work, and what does it need?

Findings (full detail in docs/research/litellm-knowledgebase.md on branch research/litellm-knowledgebase):

  1. Config shape: top-level vector_store_registry list (not under…
haylan pushed to research/litellm-knowledgebase at haylan/LLM-Server 2026-09-02 19:27:25 +00:00
a3ecbc0e02 docs(research): investigate LiteLLM knowledgebase/vector_store feature for #23
8c42f2518b research: LiteLLM web-search + SearXNG wiring (issue #22)
Compare 2 commits »
haylan created branch research/litellm-knowledgebase in haylan/LLM-Server 2026-09-02 19:27:24 +00:00