Server Setup

SpatialDrive ships as a server binary and container image. Use the release artifact selected for your deployment.

Package access requires registry credentials. The image entrypoint is the server CLI.

Dependencies

Configure PostgreSQL, blob storage, and an OIDC identity provider before serving projects. The architecture guide describes these dependencies.

The source distribution includes fdk_apps/spatial_drive/docker-compose.yml for local evaluation. It defines the dependencies, migration service, and server.

From that directory, run the published images:

docker login git.fsl.dev
docker compose up --no-build

The migration service must succeed before the server starts. Compose configures the container through its environment block. A host .env file does not automatically become the server container’s configuration.

Startup

Supply configuration for your environment, then migrate and serve:

spatial_drive --config server.toml migrate
spatial_drive --config server.toml serve

The image accepts the same commands. The Compose cli service can run commands without starting the stack:

docker compose run --rm cli config reference

Production deployment

Pin the selected release. Provision the database, storage, TLS, and identity configuration for the deployment.

The AWS ECS Fargate reference provides Terraform modules, prerequisites, and deployment steps. The authorization guide covers organizations and project access.