Configuration - alternate root path for proxied container deployment

I just set up BaGet using an nginx reverse-proxy to a container, under the location /baget/, so it is accessed at https://example.com/baget - but the interface seems to assume that baget is at the root of the domain.

How can I configure BaGet to know it is not at the root of the domain?

[KelsonBall]

Thank you - solution was to change my sites nginx configuration from

location /baget/ {
            proxy_pass         http://localhost:[BaGet port]/;
            . . .

to

location /baget/ {
            proxy_pass         http://localhost:[BaGet port]/baget/;
            . . .

After successfully adding a package though I can see that the trick for the UI definitely hasn’t fixed everything 😄

[KelsonBall]

Update - I found a closed PR that appears to have added an undocumented configuration parameter PathBase: #114

Adding PathBase=/baget does not seem to effect my https://example.com/baget/v3/index.json file. I am able to fetch the json file correctly but its data points to the root level https://example.com/api/... instead of the correct https://example.com/baget/api/... paths. As a result, trying to push a package using the dotnet cli fails, because the index.json points at incorrect paths.

Note: I seem to have mostly gotten the UI to work by adding the following to my docker startup script

docker exec -it nuget-server find /app/BaGet.UI/build/ -type f -exec sed -i -e 's/\/static/\/baget\/static/g' {} \;