Skip to main content

Deploying a Pipeline

Once you have a litejoin.yaml config (created manually or exported from Studio), deploying LiteJoin is straightforward.

CLI

The simplest deployment — run the binary directly:
LiteJoin runs in the foreground, stores data in ./data/, and logs to stdout.

Docker

Dockerfile

Docker Compose

LiteJoin uses SQLite, which requires a persistent volume. Data is lost if the container restarts without a volume mount. For crash recovery, enable Litestream replication.

systemd

Create /etc/systemd/system/litejoin.service:

Kubernetes

LiteJoin is a single-writer system. Do not run multiple replicas writing to the same data directory. For high availability, use Litestream replication with restore-on-startup.

Environment Variables

LiteJoin config files support ${ENV_VAR} expansion for secrets:
Set environment variables before starting LiteJoin. Never commit secrets to config files.

Health Checks

The SSE sink exposes a /health endpoint:
Use this for Docker HEALTHCHECK, Kubernetes liveness probes, and load balancer health checks.