# komrad start

Start the server in the background if it is not already running

[komrad](https://komrad.dev/latest/cli.md)

```bash
komrad start
```

It asks the configured address who is there first. A server already answering is left alone, whatever build it runs, so a rebuilt binary takes over only after `komrad stop`. Otherwise `komrad serve` is spawned detached, and this waits for the address to answer before returning. The server writes its own log, and what it prints when it fails to start or crashes goes to komrad-serve.out in the cache directory.

While connection.database\_url names the embedded Postgres, this starts it first if it is down, and has it reload its settings when it is up, even when the server is already running. The server starts it again whenever it exits, and `komrad stop` leaves it running.

Opening the panel does the same thing on its own, so this is for scripts and for bringing the server up without a panel.

## Inherited flags

| Flag | Type | Description |
| --- | --- | --- |
| [`--config`](https://komrad.dev/latest/cli/start.md#inherited-config) | stringArray | path to a config TOML, repeatable, later files win over earlier ones |
| [`--engine`](https://komrad.dev/latest/cli/start.md#inherited-engine) | string | engine to reach: local for this machine, or a file in the config's engines directory, layered over the config |
