fix: self-hosting doc (#2423)

This commit is contained in:
abelanger5
2025-10-15 17:52:28 -04:00
committed by GitHub
parent aa38c6d2df
commit 4e729ad9d4

View File

@@ -6,8 +6,8 @@ Self-hosting Hatchet means running your own instance of the **Hatchet Control Pl
When you self-host Hatchet, you're deploying:
- **API Server** - REST and gRPC APIs for workflow management
- **Engine** - Core workflow orchestration and task scheduling
- **API Server** - REST APIs for workflow management
- **Engine** - gRPC API for core workflow orchestration and task scheduling
- **Database** - PostgreSQL for storing workflow state and metadata
- **Message Queue (optional)** - RabbitMQ for inter-service communication and high-throughput real-time updates
- **Dashboard** - Web UI for monitoring workflows and debugging
@@ -20,7 +20,7 @@ There are currently three supported ways to self-host the Hatchet Control Plane:
Docker:
1. [Hatchet Lite](./self-hosting/hatchet-lite.mdx) - Single docker image with embedded SQLite (development, testing, or low-throughput production)
1. [Hatchet Lite](./self-hosting/hatchet-lite.mdx) - Single docker image with bundled engine and API (development, testing, or low-throughput production)
2. [Docker Compose](./self-hosting/docker-compose.mdx) - Multi-container setup with PostgreSQL and RabbitMQ (production)
Kubernetes: