docker-compose.yml

services:
  chroma:
    image: chromadb/chroma:1.5.9
    volumes:
      - chroma-data:/data
    healthcheck:
      # The v2 API. Chroma removed /api/v1 in 1.x — if you ever see a 410
      # from this container, something is talking to the old endpoint.
      test: ["CMD", "curl", "-f", "http://localhost:8000/api/v2/heartbeat"]
      interval: 5s
      timeout: 3s
      retries: 12
      start_period: 10s

  workshop:
    build: .
    depends_on:
      # Deliberately service_started, not service_healthy. If the healthcheck
      # binary is missing from the database image, gating on health would hang
      # here forever with no output. The Ruby side waits for the server itself
      # (Store.wait_for_server!) and prints something useful if it never
      # arrives.
      chroma:
        condition: service_started
    environment:
      CHROMA_URL: http://chroma:8000
    volumes:
      # Your edits to the exercises land in the container immediately, so you
      # never rebuild during the workshop.
      - ./exercises:/workshop/exercises
      - ./solutions:/workshop/solutions
      - ./test:/workshop/test
      - ./lib:/workshop/lib
      - ./data:/workshop/data
    stdin_open: true
    tty: true

volumes:
  chroma-data: