Bind app example backend to loopback and document its lack of auth
This commit is contained in:
parent
87548770a3
commit
ec787435c8
4 changed files with 9 additions and 2 deletions
|
|
@ -2,6 +2,8 @@
|
|||
|
||||
A conversational RAG interface built with [CopilotKit](https://copilotkit.ai/) and [pydantic-ai](https://github.com/pydantic/pydantic-ai)'s AG-UI protocol.
|
||||
|
||||
> **Note:** An illustrative example meant as a starting point, with no authentication. The compose files bind the backend to `127.0.0.1`; don't expose it to an untrusted network.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
- Docker and Docker Compose
|
||||
|
|
|
|||
|
|
@ -7,8 +7,9 @@ services:
|
|||
dockerfile: app/backend/Dockerfile
|
||||
command: ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8000", "--reload"]
|
||||
working_dir: /app/src
|
||||
# No authentication; bound to loopback. The frontend reaches it over the compose network.
|
||||
ports:
|
||||
- "8001:8000"
|
||||
- "127.0.0.1:8001:8000"
|
||||
environment:
|
||||
- DB_PATH=/data
|
||||
- ANTHROPIC_API_KEY=${ANTHROPIC_API_KEY:-}
|
||||
|
|
|
|||
|
|
@ -3,8 +3,9 @@ services:
|
|||
build:
|
||||
context: ..
|
||||
dockerfile: app/backend/Dockerfile
|
||||
# No authentication; bound to loopback. The frontend reaches it over the compose network.
|
||||
ports:
|
||||
- "8001:8000"
|
||||
- "127.0.0.1:8001:8000"
|
||||
environment:
|
||||
- DB_PATH=/data
|
||||
- ANTHROPIC_API_KEY=${ANTHROPIC_API_KEY:-}
|
||||
|
|
|
|||
|
|
@ -4,6 +4,9 @@ A browser-based reference implementation of conversational RAG, built on a Starl
|
|||
|
||||
This is a starting point for your own deployments, not the canonical haiku.rag UX. For the day-to-day terminal experience see [Chat](chat.md).
|
||||
|
||||
!!! warning "No authentication"
|
||||
An illustrative example meant as a starting point, with no authentication. The compose files bind the backend to `127.0.0.1`; don't expose it to an untrusted network.
|
||||
|
||||
## Features
|
||||
|
||||
- Streaming chat with real-time tool execution visibility.
|
||||
|
|
|
|||
Loading…
Reference in a new issue