Tom Kneiphof baaf8b97e1 Fix usage of WOODPECKER_ROOT_PATH (#2485) ... I had experienced some issues running Woodpecker behind a reverse-proxy, resulting from not defining the `WOODPECKER_ROOT_PATH` environment variable in #2477. As suggested by @qwerty287, specifying `WOODPECKER_ROOT_PATH=/foo` *mostly* solved the issue of running the woodpecker server at an url like `https://example.org/foo`. However, the webhook urls and badge urls were generated excluding the configured `WOODPECKER_ROOT_PATH`. This PR (mostly) fixes issues related to non-empty `WOODPECKER_ROOT_PATH`. --------- Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>		2023-09-22 16:43:31 +02:00
..
docs	Add repos list for admins (#2347)	2023-09-08 12:26:20 +02:00
flags.go	Fix usage of WOODPECKER_ROOT_PATH (#2485)	2023-09-22 16:43:31 +02:00
health.go	Fix health check (#2412)	2023-09-09 14:45:24 +02:00
main.go	Add ping command to server to allow container healthchecks (#2030)	2023-07-25 15:55:29 +02:00
server.go	Fix usage of WOODPECKER_ROOT_PATH (#2485)	2023-09-22 16:43:31 +02:00
setup.go	make WOODPECKER_MIGRATIONS_ALLOW_LONG have an actuall effect (#2251)	2023-08-21 09:29:45 +02:00
swagger.go	[Docs] use redocusaurus to display swagger file (#1818)	2023-06-04 05:07:39 +02:00
woodpecker_docs_gen.go	[Docs] use redocusaurus to display swagger file (#1818)	2023-06-04 05:07:39 +02:00