Deploy
Set up and run the TopGun server on your own infrastructure. Choose a storage backend, tune memory and connection limits, and configure the server for production. Every variable documented here traces to a real std::env::var() call in the binary — no planned-but-not-yet-supported knobs.
Self-host
Run the server with Docker, Docker Compose, or Kubernetes. Real env vars only — no TOPGUN_TLS_* or TOPGUN_CLUSTER_* that the binary doesn't read.
Self-host guide →Storage backends
Choose between redb (embedded, default), PostgreSQL (production), or null (tests only). Includes the topgun_maps table schema and migration notes.
Storage backends →Performance tuning
Tune memory eviction, write-behind buffer, and connection limits via env vars. Programmatic ServerConfig / ConnectionConfig fields for deeper control.
Performance tuning →Configuration
Operator-oriented cheatsheet: .env file examples, defaults rationale, and pre-production checklist. Links to the canonical env-var table in Reference.
Configuration →