Hi, Same question here: http://inedo.com/support/questions/3738. The git repo itself is worth caching for enterprise needs. Actually our developers checkin in the bower_components directory into their git repos, because of the "fear" that the public git repo is getting unavailable. As I can see, https://www.npmjs.com/package/private-bower has this feature. Regards Marco

Well, the NuGet API version is totally unrelated; and regarding the v3 API, it's still not stable/public yet, but they are planning a stable/public API at some point in the future (no ETA). Regarding SemVer v2 support for NuGet packages/feeds, tut The NuGet team reports they may support it in v3.5 or v3.6; if/when that happens, we'll add support for it in ProGet's NuGet feed.

It's not possible to add a new feed type via the SDK, but it's for sure on our roadmap.

Actually I was able to repro this (only when LDAP is enabled however); thank you for the report - it will be fixed in the next maintenance release v3.6.2. As a workaround, just visit the /administration/feeds/select URL directly.

Thanks- we'll try to expose these properties in the next release.

Ok thanks for the Info

This certainly used to work. It looks like nothing has changed on our end. I did some quick testing here with the latest NuGet client and can't seem to get it to send credentials with a push no matter what I do. Based on the error message you've pasted above, it looks like you're having the same issue (that message is only displayed if no auth credentials are present). You can double-check that this is happening in Fiddler, of course, but it looks like this is due to a change in behavior of NuGet.exe.

For me, using the feed name from the URL or getting it in a header makes no difference. So for me, that's not required. Thank you.

hey, i just did this on my own install by creating a new feed and adding a deny for the anonymous user for the private feed. hth, marvin

According to https://docs.inedo.com/docs/proget/feeds/other-types the Composer feed type is planned for a maintenance release of ProGet 2024, which is great news! We're currently using Satis for PHP packages alongside ProGet (for NuGet, npm, Python). Working with Satis is a bit cumbersome, that's why we would very much prefer using ProGet for PHP packages, too. Satis downloads the distribution zips for all packages and generates a static site with package metadata and the zips. I guess ProGet will handle Composer feeds in a similar fashion? Feel free to reach out to me via email if you need further feedback or beta testers for the Composer feed type.

Please note that granular, feed-based security is only available in the paid Enterprise edition. In the Express edition, privileges may only be applied to the whole system. If you would like to trial these features, you can request a trial key at https://my.inedo.com

Do you by chance have a space (or other reserved character) in the feed name? If so, make sure it is URL encoded when you access it, e.g.: http://domain.com:81/nuget/Feed Name With Spaces

You would just need to create a second feed, and then copy all of the packages on disk from one to the other.

Yet one more solution (after 6+ months). After trying all the possible solutions mentioned above - if you are still seeing the error: Response status code does not indicate success: 405 (Method Not Allowed). then most likely you need to disable your WebDav IIS plugin. You may either remove the IIS feature from the machine or if you need to keep the feature you may disable it only for this website. You may do this by editing the Web.config file (by default located here: C:\Program Files\ProGet\WebApp) and add two entries as shown below: <system.webServer> <modules> <remove name="WebDAVModule" /> </modules> <handlers> <remove name="WebDAV" /> </handlers> </system.webServer>" Note: the Modules and Handlers section should already exist, you only need to add the line <remove name="xxx"> for each section. I think Proget Dev team should integrate this in the Web.config by default to prevent future issues.. Thanks HS

Hi Simeon, Windows XP is definitely not going to be a reliable server :) The TCP stack is deliberately throttled/crippled to prevent server usage.

There is no current way (as of 3.0.0 beta) to do this built-in, but could be done with an extension. A feed adapter is probably the best way to handle this. I'm not sure what you mean by the 2nd half of your question... you don't have to pull the package to download it from a connected feed - there is a download button just the same as if it was in your private feed.

Thanks guys! The 2.0.5 release appears to have solved the connector problem.