@Dan_Woolf awesome thanks

Hi,
Do you have any recommendations to bulk upload a load of chocolatey packages which are currently in .nupkg format?

I know you can simply use powershell to retrieve all the files and then loop through and call choco push for each package but this could be slow for 1000+ packages, wondered if there was a faster approach whether that be upload using a different format or something else?

Thanks

Hi,

I wanted to ask if the ProGet technical team test any of the ProGet functionality with the new PSResourceGet module? since this is the new way for powershell to interact with the v3 API.

From my own testing I can say it works ok so far but I wanted to ask if you guys actively test and keep upto date with this module?

I've noticed a couple of issues logged on GitHub about ProGet and the PSResourceGet module so thought I would ask.

@rhessinger ok thanks

Hi,
Is it possible to configure ProGet and IIS to use a different App Pool for each feed?

I would like to have three feeds, and run each of those feeds in its own app pool, that way if one app pool misbehaves, the other app pools and feeds are not affected.

Thanks

@atripp ok, so performance wise it should not make a difference on which database option to use?, it's only recommended to go standard or enterprise if you end up enabling the high availability features.

Thanks

I know SQL standard edition is always preferred so express but does anyone have any opinions on using SQL express for ProGet?

I can't imagine the database is that utilised even for a high number of endpoints

Thanks

@atripp ok that makes sense, thanks for confirming.

@rhessinger thanks for clarification.
So that's fine as I can spin up a separate DB for each Proget install.

As long as you don't use connectors or any enterprise features, are you permitted to use the free version for business use? Is there a limit to how many free instances you can install ?

Thanks

@rhessinger thanks for confirming

Hi, I plan to use Proget on for example 6 different servers, does each instance require its own DB?
Or can you install the first instance which creates the dB, then install the second instance and point to the same dB?

This would be for the free edition and not using any connectors, the repository name would be the same on each instance

Thanks