Adapt docker compose example to use the published image

This commit is contained in:
Yiorgis Gozadinos 2026-05-27 12:59:32 +03:00
parent 1c710433c7
commit d059b59c1e
No known key found for this signature in database
3 changed files with 33 additions and 6 deletions

View file

@ -6,3 +6,6 @@ docs/
# Environment file with secrets
.env
# Local Compose override (dev builds, custom mounts, etc.)
docker-compose.override.yml

View file

@ -34,12 +34,39 @@ mkdir -p data docs
# Create config file from example (required)
cp haiku.rag.yaml.example haiku.rag.yaml
# Start services
# Start services (pulls ghcr.io/ggozad/haiku.rag-slim:latest)
docker compose up -d
```
Place documents in `docs/` for automatic indexing.
### Building locally for development
The example pulls the published image. To run a local build of
`haiku.rag-slim` instead — typical when iterating on the codebase — drop
a `docker-compose.override.yml` next to `docker-compose.yml` (the file
is auto-loaded by Compose and not checked in):
```yaml
services:
haiku-ingester:
build:
context: ../..
dockerfile: docker/Dockerfile.slim
haiku-rag:
build:
context: ../..
dockerfile: docker/Dockerfile.slim
```
Then:
```bash
docker compose build # builds & tags as ghcr.io/ggozad/haiku.rag-slim:latest
docker compose up -d # uses the local image
docker compose pull # back to the published image when done
```
## Volume Mounts
| Host Path | Container Path | Mounted on | Purpose |

View file

@ -41,10 +41,7 @@ services:
# (creating it if missing), so its /health endpoint is a valid signal
# that the DB exists — MCP waits on it via condition: service_healthy.
haiku-ingester:
build:
context: ../..
dockerfile: docker/Dockerfile.slim
image: haiku-rag-slim:local
image: ghcr.io/ggozad/haiku.rag-slim:latest
container_name: haiku-ingester
command:
[
@ -95,7 +92,7 @@ services:
restart: unless-stopped
haiku-rag:
image: haiku-rag-slim:local
image: ghcr.io/ggozad/haiku.rag-slim:latest
container_name: haiku-rag
command:
[