Version: Next 🚧

Advanced options

Why should we be happy with a default setup? We should not! Woodpecker offers a lot of advanced options to configure it to your needs.

Behind a proxy

See the proxy guide if you want to see a setup behind Apache, Nginx, Caddy or ngrok.

In the case you need to use Woodpecker with a URL path prefix (like: https://example.org/woodpecker/), add the root path to WOODPECKER_HOST.

Woodpecker supports SSL configuration by using Let's encrypt or by using own certificates. See the SSL guide.

A Prometheus endpoint is exposed by Woodpecker to collect metrics.

The autoscaler can be used to deploy new agents to a cloud provider based on the current workload your server is experiencing.

Sometime the normal yaml configuration compiler isn't enough. You can use the configuration service to process your configuration files by your own.