Deploy with Docker Compose
This page walks through a production-minded Checkpoint server on a single host with Docker Compose: choosing a database, setting addresses and secrets, the first boot, creating the first admin, and putting the server behind HTTPS. If you only want to try Checkpoint on one machine, the Quickstart is shorter.
Storage
Checkpoint keeps file content (chunked, deduplicated, compressed blocks and the version indexes that describe each changelist) separate from its database. This page covers where that content can live and how to configure it.
Configuration
This page lists every configuration file for the Checkpoint app and storage server, what each key does, and its default. For a first deployment, start with Deploy with Docker Compose.
Updates
A Docker Compose deployment updates itself from the web app. The containers run a version-independent runtime image that downloads, verifies, and runs signed Checkpoint bundles, so you never pull a new image for a new Checkpoint version. Nothing installs automatically: an instance admin decides when.
Backups
A Checkpoint server keeps its state in three places. Back up all three, regularly, and test a restore before you need one.
Authentication
This page covers how people sign in to a self-hosted Checkpoint instance: the auth secret, who may register, email and password accounts, second factors, enterprise identity providers, and how the desktop app, CLI, and CI get their credentials.
Organizations and access
Access in Checkpoint works like a small Perforce or GitHub setup: an instance admin controls who gets an account, organizations hold repositories, and roles decide who can read, write, and administer each repository.