docker-compose.yml

# Reusable block of DB connection env vars shared by every machine service.
# This is a top-level extension field (must live OUTSIDE `services:`), anchored
# with &machine-env and referenced below with *machine-env.
x-machine-env: &machine-env
  PGHOST: postgres
  PGPORT: "5432"
  PGDATABASE: plant
  PGUSER: sensors
  PGPASSWORD: sensors_pw

services:
  # ---------------------------------------------------------------------------
  # The "data warehouse": a plain Postgres instance the sensors write into and
  # Metabase reads from. In a real plant this is your IT/cloud landing zone.
  # ---------------------------------------------------------------------------
  postgres:
    image: postgres:16
    environment:
      POSTGRES_USER: sensors
      POSTGRES_PASSWORD: sensors_pw
      POSTGRES_DB: plant
    ports:
      - "5432:5432"            # exposed so you can also query with psql / DBeaver
    volumes:
      - pgdata:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U sensors -d plant"]
      interval: 5s
      timeout: 3s
      retries: 12

  # ---------------------------------------------------------------------------
  # Metabase: the open-source BI layer. Open http://localhost:3000 after start.
  # It keeps its own app state in a small embedded DB on the named volume; the
  # ANALYTICS data lives in Postgres, which you add as a data source in the UI.
  # ---------------------------------------------------------------------------
  metabase:
    image: metabase/metabase:latest
    ports:
      - "3000:3000"
    volumes:
      - mbdata:/metabase-data
    environment:
      MB_DB_FILE: /metabase-data/metabase.db
    depends_on:
      postgres:
        condition: service_healthy

  # ---------------------------------------------------------------------------
  # Three "machines" from ONE image. Same build, same script; only the CMD
  # arguments differ. This is the entrypoint/CMD pattern you asked for: the
  # `command:` here is appended after the Dockerfile ENTRYPOINT and replaces
  # the Dockerfile CMD. Each backfills history then streams live.
  # ---------------------------------------------------------------------------
  machine-cnc01:
    build: ./sensor
    environment: *machine-env
    command: ["--machine-id", "CNC-01", "--machine-type", "L",
              "--interval", "0.2", "--ideal-cycle-time", "30",
              "--backfill", "2000", "--seed", "1"]
    depends_on:
      postgres:
        condition: service_healthy
    restart: unless-stopped

  machine-cnc02:
    build: ./sensor
    environment: *machine-env
    command: ["--machine-id", "CNC-02", "--machine-type", "M",
              "--interval", "0.2", "--ideal-cycle-time", "25",
              "--down-prob", "0.04", "--backfill", "2000", "--seed", "2"]
    depends_on:
      postgres:
        condition: service_healthy
    restart: unless-stopped

  machine-press01:
    build: ./sensor
    environment: *machine-env
    command: ["--machine-id", "PRESS-01", "--machine-type", "H",
              "--interval", "0.2", "--ideal-cycle-time", "40",
              "--defect-prob", "0.06", "--backfill", "2000", "--seed", "3"]
    depends_on:
      postgres:
        condition: service_healthy
    restart: unless-stopped

volumes:
  pgdata:
  mbdata: