docs(deploy): make deploy/ describe the deployment that actually exists (#8)
Co-authored-by: claude <[email protected]>
This commit was merged in pull request #8.
This commit is contained in:
+25
-5
@@ -34,13 +34,33 @@ later co-host it.
|
||||
|
||||
## Configure the MCP server
|
||||
|
||||
```bash
|
||||
export RERANK_URL=http://10.10.1.65:8082
|
||||
# search_docs now reranks the hybrid pool through the GPU before returning
|
||||
In production the MCP reaches this sidecar **over the Drawbar compose
|
||||
network by service name**, not by host IP — `RERANK_URL` is baked into
|
||||
the image as:
|
||||
|
||||
```
|
||||
RERANK_URL=http://llama-rerank:8080
|
||||
```
|
||||
|
||||
In production (the MetaMCP-fronted Drawbar deploy), this is baked
|
||||
into the MCP server's container env.
|
||||
so the deployed `chem-mcp` service sets nothing. See
|
||||
`deploy/docker-compose.yml`.
|
||||
|
||||
That only resolves if the `llama-rerank` container is attached to
|
||||
`drawbar-backend_default`. If it is on the default bridge network
|
||||
instead, the name resolves via public DNS to an unrelated IP and
|
||||
connection-refuses — and `search_docs` falls back to dense+BM25
|
||||
**silently**. Attach it with:
|
||||
|
||||
```bash
|
||||
docker network connect drawbar-backend_default llama-rerank
|
||||
```
|
||||
|
||||
For local dev outside that network, point at the published port
|
||||
directly:
|
||||
|
||||
```bash
|
||||
export RERANK_URL=http://10.10.1.65:8082
|
||||
```
|
||||
|
||||
## Verify
|
||||
|
||||
|
||||
Reference in New Issue
Block a user