Public NuGet Gallery - built from which changeset?

Sep 30, 2011 at 3:08 AM

Hi all,

Just interested to know - what changeset in is used for the build for the public NuGet gallery (and, I guess, for the NuGet.Server package)?  We're looking to get rid of our old Orchard version and are looking for a stable build from source...

Thanks in advance, Steve

Sep 30, 2011 at 4:49 AM

Also, if we wanted to track to the same version as, what is the easiest way?  Would you guys be ok to provide changeset version detail on the site?  Or perhaps just a release note in discussions when it updates?

Sep 30, 2011 at 5:01 AM

We haven’t yet deployed the Github version of the site publicly. When we do, we’ll mark the changeset in some way. J

Sep 30, 2011 at 6:00 AM

Great!  Do you know how far away that might be?  We are  actively looking at using it internally, as the Orchard implementation we are finding incredibly resource intensive and slow enough to cause frequent publishing failures.  We are going to start some stress testing early next week hopefully, you guys happy for us to push through feedback?

Sep 30, 2011 at 6:29 AM

Yes. it would be great if you could try the new gallery and give feedback on it!

Sep 30, 2011 at 6:59 AM

In progress as we speak.  Currently stress-testing "nuget publish" over 5000 packages, will be looking at parallel next...

Sep 30, 2011 at 6:59 AM

sorry, make that "nuget push"...

Sep 30, 2011 at 1:35 PM

I have a nuget copy extension out there. The latest version will copy packages from multiple sources to multiple destinations. And I added a new command copySearch, which will copy all packages that meet the search term.

The latter seems fitting for your needs. The addextension tool worked in v1.4 (which makes installing command line extensions a breeze), let's see if it still works in the latest nuget.exe version.
"Be passionate in all you do"

Oct 4, 2011 at 8:19 AM

@ferventcoder looks good, added pull request at github for a "clone" enhancement we may end up using for migration.  Allows cloning an id or an entire source.

@haacked regarding the routes for the NuGetGallery, are you planning to support the old /package/download/{id}/{version} action?  Doesn't seem to be there at the moment (as far as I can tell).  Also, extending this to have a /package/download/{id}/latest would make a few other things we were looking at much easier.  Thoughts?

Finally, do you guys have a timeframe in mind to switch over to the new gallery/feeds?