ProGet on custom port on Docker

bishbashbosh_1120

Per the installation instructions for ProGet on Docker, it should be possible to redirect the internal port 80 externally to whatever you like, say 8080 or whatever., using docker run ... -p 8080:80

-- "If you don't want to use port 80, you can change the first port number to whatever you would like."

However, this does not work and I am seeing the same behaviour as in the referenced issue above - attempting to update packages from the feed from VS .net fails, as ProGet appears to send back a download URL to VS .net omitting the custom port (as of course it would, because it has no notion of Docker containers or any custom port mappings thereof), so the download fails.

Suggest you either remove the docker run -p suggestion from the documentation or fix it so that the port that the server listens on is also easily configurable (from an environment variable?), then the external port can mirror the internal container port and it all should work?

I seem to remember having this same issue on the Windows edition in a former life - solved it having IIS redirect a DNS alias on the server to the port that we had ProGet running on - ProGet then picks up the DNS alias for the feedback URL and it doesn't matter that it omits the port..

atripp

Hello; you'll need to change the BaseUrl in advanced settings so that ProGet can construct an absolute URL when needed (certain NuGet fields, etc). I've updated the docs to reflect this.

bishbashbosh_1120

Hi. Ah, thanks for the reminder about BaseUrl; I did have a hunt through advanced settings before posting here, but completely missed it. Still, good that you have updated the docs to reflect this - will hopefully save someone else some time. Cheers.