Server configuration

SpatialDrive settings come from environment variables, a TOML file, and built-in defaults. Environment variables take precedence over the file.

Configuration reference

The release binary generates its own settings documentation:

spatial_drive config reference
spatial_drive config schema
spatial_drive config example

reference lists settings and their environment overrides. schema emits JSON Schema. example emits the built-in defaults as TOML.

Use the output from the binary you deploy. Built-in defaults are a starting point, not a production configuration.

Configuration file

spatial_drive --config server.toml serve

Environment overrides

Nested keys use a double underscore:

DATABASE__HOST=postgres.example.internal
AUTH__ISSUER=https://identity.example.com/realms/example

A host run loads .env from the working directory without overriding values already in the process environment. For containers, provide the environment through your orchestrator.

The Terraform reference lists variables wired from module outputs and the settings your deployment supplies.

Identity and access

Use the authorization documentation to configure your provider and understand organizations, roles, and project permissions. Successful authentication alone does not grant access to every project.