Skip to main content

Build your local powershell module repository - ProGet

So Windows Powershell Blog released a blog a couple of days ago (link). Not too long after, a discussion emerged about it being to complicated to setup. Even though the required software is open source (nugetgalleryserver), it looks like you need to have Visual Studio Installed to compile it. I looked into doing it without visual stuidio, however I have been unable to come up with a solution. I even tweeted about it since I am not an developer. Maybe someone how is familiar with “msbuild” could do a post on how to do it without VS.

Anyhow one of my twitter-friends (@sstranger) came to the rescue and pointed me in the direction of ProGet, hence the title of this post. ProGet comes in 2 different licensing modes
  • Free (reduced functionality)
  • Enterprise (paid version with extra features)
The good news is that the free version supports hosting a local PowershellGet repository which was my intention anyway. So off we go and create a Configration that can install ProGet for us. This is the configuration I will use:

image

Please note we have to provide a ProductId parameter to the Package resource. Also you may tune the Arguments parameter with the options available. The documentation for silently installing ProGet is here. Basically I am installing the easy way with SQL Express and the integrated web server. The installer supports full SQL and IIS if you require that. Notice also that the path parameter is an URL pointing to the installer. A hidden feature of the Package resource in DSC.

Playing around with the installer, I used these arguments when I installed the application:

Arguments = "/S /Edition=LicenseKey /LicenseKey=R80GE44F-CFQK-NH7A38-VR4MSP-KU8Q6K9Y /Port=80 /InstallSqlExpress"

Apparently their documentation is not updated since they claim that the parameter is called Licensekeys (plural), however just drop the s and use Licensekey and you will be alright. Just incase you are wondering, that is not my licensekey :-)

So dot-source the configuration or press the green play button i ISE, run the configuration to create the MOF-file and do a Start-DSCconfiguration. If you have no idea what I am talking about, head over to powershell.org and get their free E-book on Powershell DSC. Or if you prefer just download the software and run through the installer like we did in 2003 :-)

Here is my output:

image

So let’s start your favorite web browser and navigate to http://localhost or use the name of your server:

image

You will notice that there is a default repository that links to Nuget. We don not care and will create our new PowershellGet repository.

image

We will create a feed called MSpowershell, really original. Things to notice is the API key field. Just leave it blank for now. Let’s publish a module to the repository:

image

Notice the NuGetApiKey value. It is set to the default combination of the admin user in ProGet (user:pass). If your repository have a blank API key like the one we created, that works fine. If you configure the feed with an API key, you will need to look into permissions/privileges. I have not played with it much yet, however maybe I will write another post lagter. So back to our browser, can we see a module published?

image 
And there it is. There is one final piece of the puzzle. You have to change the URL for the gallery settings in the PowershellGet module (PSGalleryPublishUri and PSGallerySourceUri). This is what I used:

image

If you ask me, it does not get any easier than this. Happy scripting and start to create your local powershell repository.

Cheers

Tore

Comments

  1. Hi, and thanks for writing a very useful and clarifying post. I have been looking for something exactly like this.
    It seems like a very simple and nice way to publish scripts for re-use. I am also interested in version control and the deploying of scripts/modules to many servers at once. It seems that maybe Inedo's other product, Buildmaster might be the answer. Any input is greatly appreciated!

    Best regards, Magnus

    ReplyDelete
    Replies
    1. It has been over a year ago since I wrote this. Things have changed a bit to say the least. Have you looked at the powershellget module? Currently it works with the powershellgallery.com website (publicly available), however you just need to update the nuget urls to use the module against for instance ProGet or a Nuget gallery.

      I have not looked at Buildmaster yet. It is on my loooong todo list.

      Cheers

      Tore
      (sorry for the late reply, been super buzy as always)

      Delete
    2. Thanks for the reply, and sorry for the double commenting on this article, didn't realize both was in queue for your approval. I will definitely check out powershellget.

      Delete
  2. This comment has been removed by the author.

    ReplyDelete
    Replies
    1. Thank you, always a pleasure to hear!

      /Tore

      Delete

Post a Comment

Popular posts from this blog

Monitoring Orchestrator runbook events from Operations Manager

Today I will follow up on my colleague’s post Mr ITblog (Knut Huglen) about monitoring Orchestrator Runbook events.  He has build a nice double up SNMP loopback feature that does self monitoring in Orchestrator resulting in entries written to a special Windows Eventlog. Now we need to raise alerts in SCOM when one of his runbooks fails or sends a platform event, who knows there could be trouble lurking in his paradise.

We are not going to do anything fancy, however these are the steps we will be focusing on today:
Create a Management Pack for our customizations Create rules that collects the events from the orchestrator serverOff we go then and fire up the SCOM console and a powershell window. First we create a MP, I am going to use powershell to do this, however you may use the SCOM console as well (Administration – ManagementPacks – Action: Create Management Pack):



Import the Management Pack into SCOM and move on to the Authoring section in the SCOM console. Create a new rule:



Give the…

Powershell – Log like you mean it

How do you do logging in powershell? Why should you do logging? What should you log? Where do you put your log? How do you remove your log? How do you search your log? All important questions and how you answer then depends upon what your background is like and the preferences you have. This will be a 2 part blog post and this is part 1.


Why should you log?

Well it is not mandatory, however I have 2 reasons:
Help with debugging a script/module/functionSelf documenting script/module/function
Firstly; Do you know any program that does not contain any bugs? Working with IT for the last 2 decades, I cannot name one. When you create scripts/modules/functions, you will create bugs, that is where they live and try to make your life a living mess.

Secondly: Adding a little extra information to your logging will make them self documenting. Do you like writing documentation? Well I normally am not fond of it and use logging while debugging to get two birds with one stone.


What should you log?

Anyt…