DevOps
Woodpecker CI
High risk: the agent mounts the Docker socket of this server, so any pipeline can control Docker (and so the whole server); only run code you trust. Needs an OAuth app you made on your forge first, with the callback address <public address>/authorize. Registration is closed; only the listed admin users can sign in.
What it does
DevOps Tool Installers
What you will be asked
You fill these in during setup.
- Web interface port RequiredAdvanced settingsThe port the web interface listens on. The default is fine unless another service already uses it.
- Forge type RequiredWhich forge you sign in with: forgejo, gitea or github. You must already have created an OAuth app there.
- Forge address OptionalThe address of your Forgejo or Gitea, for example https://git.example.com. Required for Forgejo and Gitea; ignored for GitHub.
- OAuth client ID RequiredThe client ID of the OAuth app you created on the forge. Its callback address must be exactly <public address>/authorize.
- OAuth client secret RequiredThe client secret of that OAuth app. It is written only to a root-only file on this server (mode 600) and is never printed. The characters $ ` \ and quotes are not accepted.
- Admin user names RequiredComma-separated forge user names that may sign in and administer Woodpecker. Registration is closed, so only these users can log in at first.
- Public address OptionalAdvanced settingsThe address people open Woodpecker at, without a trailing slash. Leave empty to use http://<server IP>:<web port>. The OAuth callback you registered on the forge must be this address plus /authorize.