Nugetgallery: How to create own Nuget v3 feed?

[maartenba]

_From @SharpNoiZy on November 24, 2015 6:54_

Hi, maybe I'm stupid, blind or both :)
But how do I create my own NuGet feed with v3 like I done it for v2.
Install Nuget.Server into Webproject and it was done.
But this server is nuget v2.

Kind regards

_Copied from original issue: NuGet/Home#1756_

[maartenba]

_From @emgarten on November 24, 2015 19:31_

There's no NuGet.Server v3 yet. To help with this would you tell me what your scenarios are? Will you have a v3 authenticated feed, and would you prefer that it be static content, how would you ideally want to host the v3 feed?

[maartenba]

_From @SharpNoiZy on November 24, 2015 20:21_

We have currently an private v2 feed only for our company.
I want to upgrade this to v3, to share also corefx nuget packages.

So, I need something running on one company reachable server, nothing local on my PC.

[maartenba]

_From @yishaigalatzer on November 25, 2015 1:58_

We do need to update the server, but you don't actually need a V3 server for that. @joyhui we need to update the nuget.server package.

Lets move the bug over to the nugetgallery.

[ ] we want to make sure that all the new packages are supported (DNXCORE50, generations, etc.)
[ ] use the new folder structure supported by nuget.exe init command

[maartenba]

_From @yishaigalatzer on December 31, 2015 1:27_

@maartenba is working on a new version of nuget.server, that should support your scenario.

@maartenba can you please verify that corefx packages can be hosted on the server, and can you share early bits with @SharpNoiZy

[maartenba]

@SharpNoiZy We don't have a v3 protocol server yet, but have NuGet.Server in the works with support for new target frameworks like mentioned above.

Can you try our new NuGet.Server package?

• NuGet.Server version 2.10.0-develop-0016
• From feed: https://www.myget.org/F/nugetbuild/api/v2

Or in short:
Install-Package NuGet.Server -Version 2.10.0-develop-0016 -Source https://www.myget.org/F/nugetbuild/api/v2 -IncludePrerelease

IMPORTANT do make a backup of your current NuGet.Server's packages folder in case you are upgrading. Ideally install this new package into a new server and copy over packages.

Feedback on this new version is welcome.

[maartenba]

@SharpNoiZy Have you had the chance to play with these bits?

[SharpNoiZy]

Today I had the chance to test it.
The named version "2.10.0-develop-0016" didn't work, but your latest beta version "2.10.0-ft-2843-0019" does the job! :+1:

Kind regards

[maartenba]

Sweet, thanks! Did the " develop " version throw any errors?

[SharpNoiZy]

No, not for me, everything seems to be fine until now.

[aL3891]

Hello! is there any issue tracking a protocol V3 server? i was a litte curious about writing an asp.net 5 compatible one but the spec on the wiki seems a little outdated, perhaps im just not looking in the right place?

[maartenba]

https://github.com/NuGet/NuGetGallery/issues/2632

Do know we're starting work on this soon.

[aL3891]

If you publish the spec i might be able to help :)
-edit-
oh sorry i misread, "don't know if we'll start on this soon" anywho, it would be fun to help out anyway

[maartenba]

True :-) Keep an eye on our GitHub...

[wpostma]

So due to this being open still, does that mean it is still not done?

[yishaigalatzer]

Yes it is not being implemented. Note that the V3 protocol is not required by any client and is purely optional.

Although it does provide some neat performance improvements, we are not able to prioritize this work high enough compared to other hot issues on the list.

[wpostma]

Ok. API V2 is working great.

[yishaigalatzer]

Wonderful, thanks for confirming.

[mkeymolen]

dotnet restore does't work with my private nuget server (setup with the Nuget.Server 2.11.2 package)
error: Unable to load the service index for source http://myhostname/nuget. error: The content at 'http://myhostname/nuget' is not a valid JSON object. error: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

anyone an idea how to fix this?

[yishaigalatzer]

Does nuget.exe restore work for you? It should produce the exact same results.

[wpostma]

It looks like dotnet restore is being pointed at a URL which is not a nuget feed. Maybe your URL is missing something or has something extra added. I would poke around with your browser and experiment until you find the actual URL that works with nuget. The .net application is mounted at http://myhostname/nuget and the NUGET Feed name might be something inside it like http://myhostname/nuget/nuget/ or so.

If you open your browser at http://myhostname/nuget/nuget/Packages and that works, then try http://myhostname/nuget/nuget as your feed URL.

[mkeymolen]

thanks for the feedback. i found the solution. @wpostma you pointed me in the right direction, thanks for that.
All was working fine on my windows machine but not on my Mac, so my feed was not the problem. I took a second look at my nuget.config file on my mac and than i saw a stupid mistake. Protocol version of my private package source was defined on 3. I changed it to 2 because the nuget.server package is still 2 and problem was solved. Thanks for your help!

[skofman1]

V3 protocol is not required for hosting your own NuGet feed, so adding support to NuGet.Server is not in our near term plans.
There's a community implementation allows hosting a V3 feed: https://github.com/loic-sharma/BaGet