Home

Welcome to the Transitive wiki!

Deployment modes

Transitive has four different deployment modes, one for each cell of this 2x2:

	source (with override.yaml)	self-hosted (without override.yaml)
dev	Used by Transitive developers	Used by developers at companies that want to develop their own capabilities
prod	Runs on transitiverobotics.com	Runs on a company's own domain

The docker-compose.yaml file together with docker-compose.override.yaml serve all four purposes. The docker-compose.yaml creates the distinction between dev and prod using two different docker compose profiles. If the docker-compose.override.yaml is present, as it is when deploying from a checkout of this repo, then that enables the source column. Without it, the self-hosted column is active.

In source mode, docker images are built -- from source! As a convenience for Transitive developers, we also bind-mount more folders from the host (in source-dev mode), to enable faster development.

In self-hosted mode, docker images are pulled from the dockerhub.