ProGet feeds using different app pools

forbzie22_0253

Hi,

I had a design question.

If you expect some of your feeds to be very busy, would it be better to have a separate application pool in IIS for each of the feeds in ProGet?
So one website but multiple web applications pointing to different app pools.
This way you would segregate the process etc.. so one would not affect the other.

Is this a supported configuration or do you have customers that do this?

Thanks

atripp

Hi @forbzie22_0253,

Following Microsoft's guidance to no longer use IIS for modern .NET applications, we no longer recommend using IIS to host modern versions (2022+) of our products.

Instead, you should use the Integrated Web Server instead, which is our (and Microsoft's) recommended web server. Although IIS is still supported, there are no benefits aside from a more familiar user interface.

That said, even with IIS this is not a supported nor recommended configuration; if there was ever a need to segregate feeds (for example Docker Container Images used for production applications and NuGet packages used for developers), then it should be done at an instance/server level.

Cheers,
Alana

forbzie22_0253

Does the integrated web server use Kestrel under the hood?

Assume it has feature parity with IIS so that you can have Https certificate bindings etc?

Are there any gotchas to using the integrated web server ?

Thanks

atripp

Hi @forbzie22_0253 ,

Yes, we use Kestrel under the hood.

You can configure HTTPS under Admin > HTTPS:
https://docs.inedo.com/docs/installation/installing-on-iis/installation-windows-https-support

No real "gotchas" -- but note that with port sharing (i.e. binding to a hostname as opposed to an IP), that needs to use the HTTP.SYS component of Windows.

Cheers,
Alana