> ## Documentation Index
> Fetch the complete documentation index at: https://docs.models.dunsky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run core-app locally

> Learn how to maintain and develop the Dunsky Cloud Platform: run core-app locally. Guidance based on the core-app repository.

Use Docker Compose to start the core-app frontend, backend, local PostgreSQL database, and Models API together. The stack still needs the configured external services; it is not a fully offline demo.

## Full stack

You need repository access, Docker Compose, the environment values required by `azure.env.template`, and permission to pull the Models API image from the private registry.

From the repository root, copy `azure.env.template` to `azure.env` and fill it with approved development values. Never commit this file.

```bash theme={null}
docker compose up --build
```

Open `http://localhost:3000`. The backend is also exposed on port `8081`; PostgreSQL uses `5432` and the Models API uses `8080` by default. `CORE_APP_PORT` and `CORE_APP_API_PORT` override the app ports.

Compose waits for PostgreSQL health, then runs tenancy and measures migrations and development seeding when the app starts. `RUN_DB_MIGRATIONS_ON_START=true` is a local-only convenience.

## Run packages separately

The backend requires Python 3.15 or newer:

```bash theme={null}
cd src/api
pip install -e '.[dev]'
runserver
```

The frontend pins pnpm in `src/platform/package.json`:

```bash theme={null}
cd src/platform
pnpm install
pnpm start
```

Separate backend execution needs a reachable database and the configured Databricks services for operations that use them.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.