services:
  portal-harness:
    build:
      # Keep Docker's build context limited to the browser test harness. A
      # developer may point --station-env or --output anywhere in the repo;
      # neither source credentials nor the generated two-key file may cross
      # the host-to-Docker boundary during image build.
      context: .
      dockerfile: Dockerfile
      target: ${PORTAL_HARNESS_DOCKER_TARGET:-portal-harness}
      args:
        PLAYWRIGHT_VERSION: "1.63.0"
    network_mode: host
    ipc: host
    init: true
    user: "${LOCAL_UID:-1000}:${LOCAL_GID:-1000}"
    environment:
      HOME: /tmp
      PORTAL_URL: http://192.168.4.1
      PORTAL_BROWSER_MODE: ${PORTAL_BROWSER_MODE:-auto}
      PORTAL_CUSTOM_PARAMETER_STRESS: ${PORTAL_CUSTOM_PARAMETER_STRESS:-0}
      PORTAL_PLATFORM: ${PORTAL_PLATFORM:-}
      PORTAL_CAPTURE_README_MEDIA: ${PORTAL_CAPTURE_README_MEDIA:-0}
      PORTAL_TEST_FILE: ${PORTAL_TEST_FILE:-}
      ARTIFACT_DIR: /artifacts
    volumes:
      - ${PORTAL_ARTIFACT_DIR:?portal artifact directory is required}:/artifacts