Host your own local nuget server

So you want to know how to host your own nuget server? This episode of “The Chief Tech” walks your through, in detail, exactly what you need to do to host your own private nuget server.

Why would you want to do this? Well, there are a number of reasons, the main one being to take advantage of everything nuget has to over for sharing libraries between projects without having to worry about how and where your project references them from.

In this demo, I will take you through all the steps you need to follow in order to create a local directory, be it on your machine or on a shared drive, in which you can publish your shared assemblies to as a neatly packaged nuget package.

I will also take you through the process of how to configure Visual Studio to enable access to your new local nuget source. Once this is done I will take you through the process of how to install and update new and updated nuget packages from your local source.

Initially, a lot of the work will be done through the Command Line, however at the end of the video I will take you through the necessary steps you will need to follow in order to automate the process of packaging and pushing your nuget packages every time you successfully build your shared libraries.

[georgeebisike]

This is really cool just what I needed.

[pardhasaradhi]

Excellent 👍. It's really helpful.

[mk]

When hosting the web app on a real web server, how do you get past the 406 'unacceptable' errors when trying to push packages to it?

[georgeebisike]

Please can you guild me on how to make the nugget package remotely available, but in a private domain. Take for instance a package that will be shared with different projects within the same organization