{"id":1671,"date":"2014-05-20T08:50:00","date_gmt":"2014-05-20T08:50:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2014\/05\/20\/setting-up-an-internal-powershellget-repository\/"},"modified":"2019-02-18T13:05:19","modified_gmt":"2019-02-18T20:05:19","slug":"setting-up-an-internal-powershellget-repository","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/setting-up-an-internal-powershellget-repository\/","title":{"rendered":"Setting up an Internal PowerShellGet Repository"},"content":{"rendered":"
\n

At TechEd, we announced and released an early version of PowerShellGet: a package manager for PowerShell modules.  The response was positive, and many people asked the same type of question:<\/p>\n

 <\/p>\n

“Can I set up my own internal repository for PowerShellGet?”<\/p>\n

 <\/p>\n

Many enterprise-oriented houses want the ability to create private module repositories (without sharing them with the world).  Many security minded folks want to curate their own module collections.<\/p>\n

 <\/p>\n

The short answer to this question is: yes!  All you need to do is create your own NuGet Server and redefine a couple of PowerShellGet variables.  Detailed instructions are below.<\/p>\n

Diversion: Why NuGet?<\/h2>\n

You might be asking yourself: “Why does PowerShellGet work against NuGet Feeds?” When designing PowerShellGet, we didn’t want to reinvent the wheel.  Making a good package manager from scratch can be hard.  Fortunately, Microsoft already has a pretty awesome package management solution in NuGet (http:\/\/www.nuget.org\/<\/a>).  So, we decided to build PowerShellGet on top of NuGet.<\/p>\n

 <\/p>\n

This way, we can craft a PowerShell specific package management experience without needing to develop stuff like the protocol from scratch. <\/p>\n

What does this mean for you?<\/h2>\n

This means that PowerShellGet can work against any NuGet repository out of the box.  Note: Do not publish PowerShell modules to NuGet.org.  <\/em><\/strong><\/p>\n


<\/em><\/strong><\/p>\n

The only things you need to do to make this happen are:<\/p>\n

    \n
  1. Create a NuGet repository.<\/li>\n
  2. Tell PowerShellGet to work against it.<\/li>\n<\/ol>\n

    Creating a NuGet Repository<\/h2>\n

    There are many ways to set up a working NuGet repository.  Here are a couple of options:<\/p>\n

      \n
    1. Follow the instructions in NuGet’s documentation:<\/li>\n
        \n
      1. Setting up a Local Gallery<\/a><\/li>\n
      2. Branding the NuGet Gallery<\/a><\/li>\n<\/ol>\n
      3. Let a company like MyGet to host a NuGet feed for you (https:\/\/www.myget.org\/<\/a>).<\/li>\n<\/ol>\n
        Update: Commenters have also suggested the following links for help with setting up an internal repository:<\/em><\/div>\n
        \n