Set up Pipelines-as-Code on a local Kind cluster for development.

This is meant for local development only.

Create a config file:

mkdir -p $HOME/.config/startpaac
cat <<EOF > $HOME/.config/startpaac/config
TARGET_HOST=local
PAC_DIR=~/go/src/github.com/tektoncd/pipelines-as-code
PAC_SECRET_FOLDER=~/secrets
EOF

Create your GitHub App and store the credentials:

mkdir -p ~/secrets
for i in github-application-id github-private-key smee webhook.secret; do
  ${EDITOR:-vi} ~/secrets/$i
done

Run the interactive installer:

./startpaac

Core (always): Kind cluster, Nginx ingress, Docker registry, Tekton Pipelines

Optional (selected via menu): PAC (built from local source with ko), Tekton Dashboard, Tekton Triggers, Tekton Chains, Forgejo, PostgreSQL, GitHub second controller

./startpaac              # interactive install (or uses saved preferences)
./startpaac -a           # install everything non-interactively
./startpaac -p           # redeploy PAC from source
./startpaac -c controller  # redeploy a single component (controller/watcher/webhook)
./startpaac --menu       # force the interactive menu
./startpaac --stop-kind  # tear down the cluster

Configure PAC on an existing cluster (e.g. OpenShift):

./startpaac --configure-pac-target $KUBECONFIG $TARGET_NAMESPACE $SECRET_FOLDER

Minimal config in ~/.config/startpaac/config:

TARGET_HOST=local
PAC_DIR=~/path/to/pipelines-as-code
PAC_SECRET_FOLDER=~/secrets

See docs/configuration.md for the full reference (remote VM setup, secrets management, hooks, PostgreSQL, preferences).

docker, kind, helm, kubectl, jq, minica

Optional:

• ko - only needed when deploying PAC from source (-p, -a, -c flags)
• gum - enhances interactive menus (falls back to plain bash prompts)
• pass - for secrets management

macOS users: install coreutils and gnu-sed from Homebrew.

• Configuration reference
• Architecture
• ZSH completion