# noust compose

Look at a Docker Compose document before it is deployed.

```bash
noust compose [OPTIONS] COMMAND [ARGS]...
```

Subcommands: [`check`](#noust-compose-check), [`import`](#noust-compose-import)

## noust compose check

Say what a Compose document is, without running it.

```bash
noust compose check [OPTIONS] FILE
```

Arguments: `file`

| Option | What it does | Default |
|---|---|---|
| `--json` | Print the analysis as JSON. |  |
| `--reason` | Why this change is made (a change reference, a ticket). Recorded with the command in the audit log; required only where a compliance framework asks for it (ENS) or security.change_reasons is on. |  |

## noust compose import

Turn a Coolify or Dokploy service template into a Compose document Noust deploys.

```bash
noust compose import [OPTIONS] FILE
```

Arguments: `file`

| Option | What it does | Default |
|---|---|---|
| `--from` | Whose template FILE is. | `coolify` |
| `--template` | dokploy: the template's template.toml (read from FILE's folder when FILE is a folder). |  |
| `--domain` | The name the stack will be served on (fills its address variables). |  |
| `--port` | The host port of the web service on 127.0.0.1 (a free one by default). |  |
| `--out` | Write docker-compose.yml and .env (0600, with the generated secrets) into this folder, and the files a Dokploy template mounts. |  |
| `--json` | Print what was made as JSON (never the secrets). |  |
| `--reason` | Why this change is made (a change reference, a ticket). Recorded with the command in the audit log; required only where a compliance framework asks for it (ENS) or security.change_reasons is on. |  |