Documentation

Deployment

Run Kite in production — Docker, CI/CD integration, and environment variables.

// 01Running the CLI in production

The kite binary is a single static executable with no runtime dependencies. Copy it to any environment and run it directly:

bash

# In a Dockerfile
COPY kite /usr/local/bin/kite

# Or install via the script at build time
RUN curl -sSL https://getkite.sh/install | sh

Environment variables

Variable	Description
`KITE_API_KEY`	API key, overrides config file
`KITE_SERVER`	Relay server URL (default: `https://relay.getkite.sh`)
`KITE_CONFIG`	Path to config file (default: `~/.config/kite/config.toml`)

Set KITE_API_KEY in your CI secrets or container environment instead of using the device auth flow.

// 02Docker

dockerfile

FROM debian:bookworm-slim

RUN curl -sSL https://getkite.sh/install | sh

ENV KITE_API_KEY=your_key_here

CMD ["kite", "proxy", "--source", "github", "--target", "http://app:3000/webhooks"]

// 03CI/CD integration

Use Kite in GitHub Actions to receive webhook events during test runs:

yaml

- name: Start Kite proxy
  env:
    KITE_API_KEY: ${{ secrets.KITE_API_KEY }}
  run: |
    kite proxy --source github --target http://localhost:3000/webhooks &
    echo "KITE_PID=$!" >> $GITHUB_ENV