compose.dev.yml

# Local development override — builds images from source instead of pulling
#
# Preferred usage:
#   bun run dev:build
#
# Manual equivalent (from project root):
#   docker compose --project-directory . \
#     -f .openpalm/config/stack/core.compose.yml \
#     -f compose.dev.yml \
#     --env-file .dev/knowledge/env/stack.env \
#     up --build -d
#
# The --project-directory . flag is REQUIRED when the core compose file lives
# in a different directory (.openpalm/config/stack/ or .dev/config/stack/).
# Without it, Docker Compose resolves build contexts relative to the first -f
# file's directory, which breaks builds.

services:
  guardian:
    build:
      context: .
      dockerfile: containers/guardian/Dockerfile
      args:
        # The guardian Dockerfile bakes @openpalm/guardian@${GUARDIAN_VERSION}
        # at build time and hard-fails (`test -n`) if it is empty. Compose does
        # not forward host env into ARGs unless declared here. Callers that need
        # an exact version (the rootless smoke fixture, release builds) export
        # GUARDIAN_VERSION; a bare `bun run dev:build` falls back to the latest
        # published guardian, which keeps the guard satisfied.
        GUARDIAN_VERSION: ${GUARDIAN_VERSION:-latest}
    image: ${OP_IMAGE_NAMESPACE:-openpalm}/guardian:dev
    # Guardian is intentionally NOT host-published. It is reachable only on
    # the portal_net / assistant_net networks as `http://guardian:8080`.
    # Manual smoke tests that previously hit a host-published port must
    # either run inside the network or use `docker exec openpalm-guardian-1`.

  assistant:
    build:
      context: .
      dockerfile: containers/assistant/Dockerfile
    image: ${OP_IMAGE_NAMESPACE:-openpalm}/assistant:dev

  portal:
    build:
      context: .
      dockerfile: containers/portal/Dockerfile
    image: ${OP_IMAGE_NAMESPACE:-openpalm}/portal:dev