This Docker container is the simplest NuGet server possible so it only supports the one feed. Create different feeds for different package types.
#Nexus nuget repository install#
If you called Install-Package on a module, it does not install it like Install-Module would. Running Find-Package would list your modules. I found that having them in the same feed creates a lot of clutter and makes your feed more confusing. But I do recommend that you do not mix modules and regular packages. We package all of our software installs as NuGet packages and distribute them with Install-Package. The focus of this article was on Modules, but you can use NuGet to distribute other packages too. This is the same API key we specified when setting up the server. Publish-Module -Name MyModule -Repository MyRepository -NuGetApiKey $apiKey Here is the command that I ran to start this instance. The sunside/simple-nuget-server was the first container that I could find. For todays post, we are going to spin up a local instance in Docker. If you are already using VSTS (Visual Studio Team Services), they have a NuGet Package Management offering that you can use. The Microsoft docs site has a good list here: Hosting your own NuGet feeds. There many options for creating your own site to host feeds and there are a few pre-built servers available. The first thing we need is a NuGet server. With Docker, you will see it is just as easy to test with a NuGet feed.
If you open access up to your DMZ, those systems can pull modules off this feed.Ī file share is fine for local testing but for production you want a NuGet feed. This is just a website when it comes down to it.
The NuGet feed will scale much better because it indexes the packages as they are uploaded.Ī NuGet feed also makes it easy to distribute modules to systems that are not part of your domain. This is how we manage our modules internally.Ī NuGet server or feed is the reccomended way to distribute your modules. I am going to take that idea to the next step and publish a module to a NuGet server.
In my post talking about Your first internal PSScript repository, I used a network share to show how easy it is to get started.