woodpecker/server/forge/gitea
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
..
fixtures Change master to main (#2044) 2023-07-31 05:47:23 +02:00
gitea.go Fix usage of WOODPECKER_ROOT_PATH (#2485) 2023-09-22 16:43:31 +02:00
gitea_test.go make EqualStringSlice to generic EqualSliceValues (#2179) 2023-08-09 09:00:12 +02:00
helper.go Add SSH clone URL env var (#2198) 2023-08-12 17:39:13 +02:00
helper_test.go make EqualStringSlice to generic EqualSliceValues (#2179) 2023-08-09 09:00:12 +02:00
parse.go let HookParse func explicit ignore events (#1942) 2023-07-14 02:03:54 +02:00
parse_test.go make EqualStringSlice to generic EqualSliceValues (#2179) 2023-08-09 09:00:12 +02:00
types.go Rename remote to forge (#1357) 2022-11-05 00:35:06 +01:00