Manage deployment configuration with external automation ​

Coordinator DB does not provide a documented Terraform provider or hosted-service provisioning API. Use your infrastructure tooling to manage the host, network, service startup and configuration files. Use the SQL interfaces for database objects and data.

Define the external resources ​

Choose the database file location, native and optional HTTP listener addresses, existing XML configuration path and credentials file. Relative configuration paths have documented rules: user and log paths start at the configuration directory, while an explicit relative --config-file starts at the working directory.

The server does not generate missing configuration files. Automation should place complete validated files before startup and keep secrets out of public plans, logs and version-controlled examples. File edits require a restart to take effect.

Verify the result ​

After the service starts, test /ping when HTTP is enabled, then run an authenticated SELECT 1 against the intended database. Apply schema migrations as an explicit separate step so a network failure is not confused with a SQL migration failure.

A declarative infrastructure run does not prove that the database contains the required tables or that an application can use its route. Capture both deployment success and the small SQL verification result in your own workflow.

See configuration files, command-line options and HTTP readiness.