> ## 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.

# Configure development environments

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

core-app separates Docker environment configuration, standalone backend configuration, and frontend build settings. Use the template for the execution mode you choose.

| Mode | Configuration |
| - | - |
| Docker Compose | Root `azure.env`, copied from `azure.env.template` |
| Standalone backend | `src/api/.env.local`, copied from `.env.local.example` in that directory |
| Frontend development | `src/platform/.env.local` with `VITE_*` values |

## Database connection

`LAKEBASE_DATABASE_URL` supplies a static database connection and bypasses credential minting. Otherwise, the backend builds a connection from `LAKEBASE_HOST`, `LAKEBASE_PORT`, `LAKEBASE_DATABASE`, and `LAKEBASE_INSTANCE_NAME` and mints a short-lived credential using the Databricks SDK. `LAKEBASE_PORT` defaults to `5432`.

Set `DATABRICKS_HOST` to the workspace used by the SDK. The standalone backend loads its local environment file automatically without overriding values already present in the process environment.

## Frontend and identity

Frontend settings include `VITE_B2C_*`, the API base URL, and the Mapbox token. Backend group settings distinguish platform administrators and internal users. Keep deployment credentials in the approved secret stores; do not copy real values into documentation or Git.

> [!NOTE]
>
> Use the checked-in templates as the complete variable inventory. This page documents the main configuration boundaries rather than reproducing every setting.


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