---
title: Command and configuration reference
description: Find Compose commands, source startup options, and runtime directory settings.
lastVerified: 2026-09-23
---

# 7.1 Command and configuration reference

For everyday use, follow the installation guide first. Change configuration only after understanding where it applies and what it affects.

Commands on this page apply to the current Compose and source workflows. The native npm installer has not been published, so its planned installation, lifecycle, backup, and upgrade commands are not listed as executable instructions. See the [installation guide](https://docs.teloa.ai/markdown/en/start/quickstart.md) for runtime options and local execution boundaries.

## Compose commands

Run these in the source directory containing `compose.yaml`:

```sh
docker compose up -d --build
docker compose ps
docker compose logs --tail=50 app
docker compose stop
docker compose start
```

Logs may contain the current authentication URL. View them in your own terminal and do not paste them directly into a public issue. `stop` preserves containers and data volumes. Do not use options that delete data volumes as a routine way to restart.

## Configuration options

| Name | Default | Purpose |
| --- | --- | --- |
| `TELOA_PORT` | `3100` | Web port mapped to the local host by Compose |
| `TELOA_DSH_PORT` | `3100` | Internal host port when running from source; fixed inside Compose |
| `TELOA_DSH_HOME` | `.runtime/dsh` | DSH runtime directory when running from source |
| `TELOA_RUNTIME_ROOT` | `.runtime/teloa` | Business runtime directory when running from source |
| `TELOA_WORKSPACE_ROOT` | `workspace` under the runtime directory | Working files and the default sandbox working directory |
| `TELOA_DSH_PROFILE` | `teloa` | Runtime profile identity |

Compose stores runtime directories under `/data` in persistent volumes. Changing a directory or profile does not migrate existing data. Acceptance environments require the full set of isolation parameters; use the dedicated launcher.

Configure model credentials through the provider settings in **Settings**, not through these port variables. Users remain responsible for model usage costs in every distribution option.