# Verify a macOS build

Verify a macOS executable on the Mac that will run it. Record whether the machine is Apple silicon or Intel and whether the process runs directly or through a compatibility environment. Keep those results separate when comparing distributions.

Follow [installation](https://coordinatordb.com/docs/get-started/setup/install) for the current installation procedure. Place the resulting executable and the supplied configuration files in a dedicated directory rather than running against an application database.

## Check the local environment

```sh
uname -m
sw_vers -productVersion
./coordinator serve --config-file config.xml --db data.db
```

Then use another terminal in that directory:

```sh
./coordinator client --database data --query "SELECT 'macOS' AS platform FORMAT csv"
```

Expect a single CSV value, `"macOS"`. Confirm that the server can create the selected database and write its configured logs under the same account used for the check.

## Check paths explicitly

Use a path containing spaces when an application or packaging change affects file selection. Quote that path in the shell and verify the configured database independently of the configuration directory. See [configuration files](https://coordinatordb.com/docs/concepts/features/configuration/server-config/configuration-files) and the [native client](https://coordinatordb.com/docs/concepts/features/interfaces/client) for path and connection options.