# Woodpecker CI pipeline for co-op/docs — THIN and SECRET-FREE on purpose. # # It does NOT deploy. Publishing is host-side and split: # # /usr/local/sbin/docs-poll host-owned poller (root) — pulls main # publishing/build.sh runs as the unprivileged `docsbuild` user, # with no credentials and no access to # /home/ubuntu # /usr/local/sbin/docs-publish root-owned publish step — runs no repo code, # holds the Cloudron token from a root-only file # # CI exists only to prove the repository builds. It runs in a throwaway venv # inside the pipeline workspace, never the agent image's shared /opt/docs-venv: # a push to ANY repo must not be able to change a toolchain that another # pipeline uses. No secret is wired into this pipeline, and none should be # until the Woodpecker agent supports per-pipeline isolation. # # Backend note: the co-op's Woodpecker agent is a Cloudron app with no Docker # socket, so it uses Woodpecker's `local` backend. Each step runs as a shell # command INSIDE the agent container; the `image:` field selects the SHELL, not # a container image. That is exactly why this file must stay secret-free: the # container is shared by every pipeline. when: - event: manual steps: - name: build image: bash commands: # Ephemeral toolchain per run — no shared venv, no /opt/docs-venv. - python3 -m venv .ci-venv - .ci-venv/bin/pip install -q -r publishing/requirements.txt - publishing/build.sh .ci-venv