multica-ai / multica

Get started

Taken from the repository's own files on 24 Oct 2026. RepoPilot has not run these commands.

package.json

Task	Run	What it runs
build	`pnpm run build`	`turbo build --filter=!@multica/mobile`
test	`pnpm run test`	`turbo test --filter=!@multica/mobile`
lint	`pnpm run lint`	`turbo lint --filter=!@multica/mobile`
typecheck	`pnpm run typecheck`	`turbo typecheck --filter=!@multica/mobile`

No installation or usage section was found in the README. Read the README

CONTRIBUTING.md

Local development uses one shared PostgreSQL container and one database per checkout.

the main checkout usually uses .env and POSTGRES_DB=multica
each Git worktree uses its own .env.worktree
every checkout connects to the same PostgreSQL host: localhost:5432
isolation happens at the database level, not by starting a separate Docker Compose project
backend and frontend ports are still unique per worktree

This keeps Docker simple while still isolating schema and data.

Taken from the repository's own files on 24 Oct 2026. RepoPilot has not run these commands.

package.json

Task	Run	What it runs
build	`pnpm run build`	`turbo build --filter=!@multica/mobile`
test	`pnpm run test`	`turbo test --filter=!@multica/mobile`
lint	`pnpm run lint`	`turbo lint --filter=!@multica/mobile`
typecheck	`pnpm run typecheck`	`turbo typecheck --filter=!@multica/mobile`

No installation or usage section was found in the README. Read the README

CONTRIBUTING.md

Local development uses one shared PostgreSQL container and one database per checkout.

the main checkout usually uses .env and POSTGRES_DB=multica
each Git worktree uses its own .env.worktree
every checkout connects to the same PostgreSQL host: localhost:5432
isolation happens at the database level, not by starting a separate Docker Compose project
backend and frontend ports are still unique per worktree

This keeps Docker simple while still isolating schema and data.