This guide covers running project services directly on the host without Docker Compose-managed application containers.
Use this path when you need direct debugger access, custom local process control, or faster single-service iteration. For Docker-based hot reload, see Docker development setup. For production-style deployment, see Production setup.
Install these tools on the host:
pnpm- Go
uv- PostgreSQL 18.4
- Redis
PostgreSQL and Redis must already be running locally before starting application services.
Use the dev environment template as the starting point:
cp -n deploy/docker/.env.dev.example deploy/docker/.envIf you run services outside Compose, make sure host-facing values are used for PostgreSQL, Redis, and service URLs. The dev template defaults are intended for local development and direct ports.
pnpm install --filter frontend...
pnpm --dir frontend devDefault URL:
http://localhost:3000
cd backend
go run ./cmd/apiDefault URL:
http://localhost:8080
cd ai-service
uv run uvicorn main:app --reloadDefault URL:
http://localhost:8000
cd browser-worker
go run .Default URL:
http://localhost:8081
The browser worker uses Docker to create isolated browser runtime containers. Make sure Docker is running and reachable from the host if you use remote browser sessions.
pnpm install --filter collab-service...
pnpm --dir collab-service devDefault URL:
http://localhost:8090
cd content-pipeline-service
cargo run -p content-pipeline-serviceDefault gRPC address:
localhost:50051
pnpm install --filter mpp-extension-publisher...
pnpm --dir extension devDefault URL:
http://localhost:3010
Load extension/.output/chrome-mv3-dev as an unpacked extension in the host browser.