# Managed Portal Deployment Findings

## Local
- Project root: `/Users/yoilun/code/managed-portal`.
- Existing Docker files: root `Dockerfile`, `deploy/docker-compose.yml`, managed service Dockerfiles.
- Git worktree has uncommitted changes; deployment should use the current filesystem state.
- Docker Compose services: `managed-portal`, `store-dwell-alert`, `people-flow-project`, `managed-portal-web`.
- Compose exposes web UI on `${MANAGED_PORTAL_WEB_PORT:-13000}` and uses `restart: unless-stopped` for all services.
- Model weights/assets found:
  - `managed/people_flow_project/weights` is about 1.1G and includes YOLO plus DeepFace `.h5` files.
  - `managed/store_dwell_alert/weights` is about 5.4M and includes `yolo11n.pt`.
- Root `.dockerignore` excludes `managed`, but the managed service images build from their own contexts under `managed/`, so their weights remain part of those build contexts.

## Remote
- Host `192.168.5.185` is Ubuntu Linux x86_64, kernel `6.8.0-111-generic`.
- User `xiaozheng` has sudo group membership.
- Disk space: `/` has about 824G available.
- Docker is installed: `Docker version 29.4.2`.
- Docker Compose is installed: `Docker Compose version v5.1.3`.
- `systemctl` is available.
- Remote deploy path: `/home/xiaozheng/code/managed-portal`.
- Remote GPU: NVIDIA GeForce RTX 3080, with Docker `nvidia` runtime available.
- Remote weight files verified by path and byte size.
- Docker service is enabled on boot.
- Running containers:
  - `managed-portal`
  - `managed-portal-web`
  - `people-flow-project`
  - `store-dwell-alert`
- `people-flow-project` and `store-dwell-alert` report healthy in Compose.
- Web UI is exposed on `http://192.168.5.185:13000/`.
- Managed services API is available through the web proxy at `/api/managed-services`.