Local Quickstart
April 26, 2026 ยท View on GitHub
This guide is the shortest path for a new contributor to run DeepEye locally and validate that the development environment works.
Prerequisites
- Docker and Docker Compose
uv- Node.js 20 and npm, only when running frontend checks outside Docker
- An LLM API key and model name
1. Configure Environment
cp env.example .env
Edit .env and set at least:
COMPOSE_PROJECT_NAMEHOST_GATEWAY_PORTLLM_API_KEYLLM_BASE_URLLLM_MODELJWT_SECRET_KEYPOSTGRES_PASSWORDMINIO_ACCESS_KEYMINIO_SECRET_KEYDOCKER_CONTROL_API_KEY
Use unique values on shared machines to avoid container, volume, and port conflicts.
2. Validate Configuration
make compose-config
This checks that Docker Compose can parse the stack and environment.
3. Start DeepEye
docker compose up --build
Open:
http://localhost:8080
If you changed HOST_GATEWAY_PORT, use that port instead.
4. Confirm Services
In another terminal:
docker compose ps
The important services are:
gatewayfrontendbackend-apibackend-workerruntime-controlpostgresredisminio
For a deeper smoke test after the stack is running:
make compose-smoke
5. Try A Minimal Workflow
Use the UI to create a session, attach a small CSV, and ask for a simple report or summary. For reference data and scenario notes, see:
6. Run Local Quality Checks
Fast backend/core check:
make check-python
Full local CI equivalent:
make check
Install dependencies before checking:
make check-install
Troubleshooting
Port Already In Use
Set a different HOST_GATEWAY_PORT in .env, then restart the stack.
Docker Permission Errors
Confirm your user can run:
docker ps
If not, fix local Docker permissions before running DeepEye.
Startup Warmup Fails
Check LLM_API_KEY, LLM_BASE_URL, LLM_MODEL, and provider network access.
For local debugging only, you can temporarily set:
STARTUP_WARMUP_STRICT=false
Reset Local Data
This removes local containers and volumes for the current Compose project:
docker compose down -v
Only use this when you intend to delete local development data.