fleet-memory/docker/services
Nicolò Boschi 3e72984cd2 chunks
2025-11-29 16:34:13 +01:00
..
api.Dockerfile chunks 2025-11-29 16:34:13 +01:00
build-all.sh chunks 2025-11-29 16:34:13 +01:00
control-plane.Dockerfile chunks 2025-11-29 16:34:13 +01:00
docker-compose.yml chunks 2025-11-29 16:34:13 +01:00
README.md chunks 2025-11-29 16:34:13 +01:00

Distributed Hindsight Setup

Run API and Control Plane as separate containers.

Start

cd services
docker-compose up

Access:

What's Running

Two separate containers:

  • api - Hindsight API with embedded pg0 database
  • control-plane - Web UI

Build Images

./build-all.sh

Creates:

  • hindsight/api:latest
  • hindsight/control-plane:latest

Configuration

The API uses embedded pg0 by default. Database files are stored in the api_data volume.

To use an external PostgreSQL database, add to docker-compose.yml:

services:
  api:
    environment:
      HINDSIGHT_API_DATABASE_URL: postgresql://user:pass@host:5432/db

Data Persistence

docker-compose down -v  # Remove volumes

Why Use This?

The distributed setup is useful when you want to:

  • Scale API and UI independently
  • Use an external database in production
  • Deploy to Kubernetes/orchestration
  • Run UI on different infrastructure

For simple deployments, use the main docker-compose.yml (standalone all-in-one).