Nuget server setup

Now that you have the NuGet. Server files on your web server, open IIS manager, right-click on the default web site and select New Application as shown below. Provide a name for the application. Take note of the package URI on the page. You will need this for later. You can also map the package folder to another path. This could be used when you have a small drive that you have the web server files on, but you have another drive that is larger for containing the packages.

To change the package path change the packagesPath value in the web. Once you are done making your changes to the web. Take a look at the web. By default, the API key is blank. When an API key is added, you will be required to use this every time you need to add or delete packages from the repository.

Once the key is added to the value for apiKey save the file. You can instead change the value for requireApiKey to false to not need an API key to add or delete packages. Now you have your NuGet. Server is a Nuget package manager and has frequent updates that you will want to take advantage of. To update a NuGet. Server, open your previous project. This is the same path where your project is built that you located earlier. Or if you open Visual Studio, it may be listed in your recent projects.

From here you can see all the packages that have updates. Select NuGet. Server and click update as shown below. This will update NuGet. Server and all the dependencies that require updates. At this point, you should now have a brand new NuGet. Server instance running on your machine. Congratulations on setting that up! But this step is just the beginning. Nuget server setup Ask Question. Asked 9 years, 11 months ago. Active 9 years, 6 months ago.

Viewed 3k times. Is there a way of setting up different api keys for every user? Improve this question. Add a comment. Active Oldest Votes. Improve this answer. Matthew Skelton Matthew Skelton 2, 19 19 silver badges 21 21 bronze badges. Sumo Sumo 3, 21 21 silver badges 40 40 bronze badges. Xavier Decoster Xavier Decoster Sign up or log in Sign up using Google.

This is something else to keep in mind if you are looking to go down this route. MyGet seems to be the consensus best hosted solution out there if you are looking for something outside the Microsoft eco-system.

I had a quick play around with MyGet but nothing too indepth and honestly it seemed pretty solid. Something that was interesting to me was that MyGet will actually build your nuget packages for you, all you need to do is give it access to your source control.

The pricing for VSTS works in two ways. The alternative to using a hosted solution is to have an on-premises private nuget feed Or possibly on a VM. You can check out instructions to get it up and running here. Now this was actually my preferred option at first.

To keep control of the packages and have complete control of the hosting seemed like the best option. But that quickly changes for a few reasons…. This seemed like a pretty big deal breaker.

There is an API Key authorization that you can set in the web. This in itself seemed like an annoyance because it meant that the keys to the kingdom was an API Key and with that you could essentially do what you liked with it. This means you had to use actual hardware like a VM or host it locally on a machine.