Deploy OpsKnight with Docker Compose

Docker Compose is the maintained single-host path. It supports integrated or split runtime, bundled or external PostgreSQL, and split-mode PgBouncer.

Choose an installation

• Start with Prerequisites.
• Choose Integrated runtime for the simplest small installation.
• Choose Split runtime for isolated runtime roles and role-specific scaling.
• Add External PostgreSQL when the database is operator-managed.
• Add PgBouncer only to a supported split topology.
• Put the application behind a TLS reverse proxy.
• Complete public HTTPS initial setup and verify the Application URL.

Use the same ordered Compose file list for every command. Store that list in the deployment runbook. Omitting or reordering an overlay can start the wrong ownership model.

Lifecycle guides

• Upgrade a Compose deployment
• Troubleshoot Compose
• Production acceptance checklist
• Reverse-proxy contract
• Back up and restore

Scope and availability

Compose persists state across container replacement, but it does not reschedule workloads onto another host. Host failure remains an outage until the host or deployment is recovered. Choose Swarm or Kubernetes when automatic multi-node rescheduling is required.