mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2024-05-22 02:08:07 +00:00
dda4998261
As discussed in the comments in PR #1197. Also add documenation accordingly. One thing I'm not sure about is the simple check in health.go if the address is usable in the GET request or not. From reading https://pkg.go.dev/net#Dial it seems that the only non-standard address format that would work in the `net` package but not in a GET url would likely only be `:port`, as the others listed here are actually also valid urls: `For TCP, UDP and IP networks, if the host is empty or a literal unspecified IP address, as in ":80", "0.0.0.0:80" or "[::]:80" for TCP and UDP, "", "0.0.0.0" or "::" for IP, the local system is assumed.` One additional thing I noticed is that while `WOODPECKER_SERVER_ADDR` and `WOODPECKER_SERVER_ADDR` use the default value format of `:PORT`, `WOODPECKER_SERVER` actually uses `localhost:9000`. I guess it makes a bit of sense, considering the server might not be local to the agent, but it looks a bit inconsistent this way. I don't think it would hurt to make the `WOODPECKER_HEALTHCHECK_ADDR` in this format too, but then it's different from the server flags again... :-) |
||
|---|---|---|
| .. | ||
| 11-forges | ||
| 22-backends | ||
| 00-setup.md | ||
| 10-server-config.md | ||
| 15-agent-config.md | ||
| 30-database.md | ||
| 60-ssl.md | ||
| 70-proxy.md | ||
| 80-kubernetes.md | ||
| 90-prometheus.md | ||
| 100-external-configuration-api.md | ||
| _category_.yml | ||