Verify the SearXNG search, embedding-server, pgvector-db, and litellm-pgvector wiring on the real R9700 box: does docker compose up -d embedding-server pgvector-db litellm-pgvector come up healthy, does litellm-pgvector's Prisma migration run correctly against a fresh pgvector-db on first boot, does /v1/search/searxng-search actually reach SearXNG through the extra_hosts DNS fix, does the vector_store_registry config in litellm-config.yaml actually work against the deployed ghcr.io/berriai/litellm:main-stable image (field names for the pg_vector provider were not independently confirmed against a running deploy — see docs/research/litellm-knowledgebase.md), and does scripts/ingest-memory.sh + a file_search tool-call query round-trip real content from data/memory.md.
## Question
Verify the SearXNG search, embedding-server, pgvector-db, and litellm-pgvector wiring on the real R9700 box: does `docker compose up -d embedding-server pgvector-db litellm-pgvector` come up healthy, does `litellm-pgvector`'s Prisma migration run correctly against a fresh pgvector-db on first boot, does `/v1/search/searxng-search` actually reach SearXNG through the `extra_hosts` DNS fix, does the `vector_store_registry` config in `litellm-config.yaml` actually work against the deployed `ghcr.io/berriai/litellm:main-stable` image (field names for the `pg_vector` provider were not independently confirmed against a running deploy — see docs/research/litellm-knowledgebase.md), and does `scripts/ingest-memory.sh` + a `file_search` tool-call query round-trip real content from `data/memory.md`.
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 connector. Concretely: does docker compose up -d embedding-server pgvector-db memory-retrieval come up healthy, does PGVector create its tables correctly against a fresh pgvector-db on first use, does POST /ingest + POST /query round-trip real content, and does scripts/ingest-memory.sh load data/memory.md/data/claude-legacy-memory.md successfully. The SearXNG /v1/search and extra_hosts verification is unchanged from the original scope.
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` connector. Concretely: does `docker compose up -d embedding-server pgvector-db memory-retrieval` come up healthy, does `PGVector` create its tables correctly against a fresh `pgvector-db` on first use, does `POST /ingest` + `POST /query` round-trip real content, and does `scripts/ingest-memory.sh` load `data/memory.md`/`data/claude-legacy-memory.md` successfully. The SearXNG `/v1/search` and `extra_hosts` verification is unchanged from the original scope.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Question
Verify the SearXNG search, embedding-server, pgvector-db, and litellm-pgvector wiring on the real R9700 box: does
docker compose up -d embedding-server pgvector-db litellm-pgvectorcome up healthy, doeslitellm-pgvector's Prisma migration run correctly against a fresh pgvector-db on first boot, does/v1/search/searxng-searchactually reach SearXNG through theextra_hostsDNS fix, does thevector_store_registryconfig inlitellm-config.yamlactually work against the deployedghcr.io/berriai/litellm:main-stableimage (field names for thepg_vectorprovider were not independently confirmed against a running deploy — see docs/research/litellm-knowledgebase.md), and doesscripts/ingest-memory.sh+ afile_searchtool-call query round-trip real content fromdata/memory.md.Updated scope after #25: this ticket now verifies
memory-retrieval(thelangchain_postgres.PGVector-based service,services/memory-retrieval/) instead of the retiredlitellm-pgvectorconnector. Concretely: doesdocker compose up -d embedding-server pgvector-db memory-retrievalcome up healthy, doesPGVectorcreate its tables correctly against a freshpgvector-dbon first use, doesPOST /ingest+POST /queryround-trip real content, and doesscripts/ingest-memory.shloaddata/memory.md/data/claude-legacy-memory.mdsuccessfully. The SearXNG/v1/searchandextra_hostsverification is unchanged from the original scope.