Saturday, October 4, 2014

Setting up an Internal PowerShellGet Repository

Advertise

@John

I am very pleased that you will chat with me, I will try my best to chat with you ;-)

But..

I am very busy to do ma daily work, to  coordinate the German PowerShell Community, produce German PowerShell videos for my YouTube channel and to do Forum Support on TechNet.

Even I do Twitter, Facebook Google+ all with PowerShell Stuff.

So it is very hard for me to coordinate and doing additional conversations on so many different Places.

So please bear with me if I miss a Post.

Event it is hard for me to chat in English, English Post take me long time :-(

I think the most conversation is already done in the community.

The First Time I saw the discussion about the need of a PowerShell module manager I was very excited about the idea because I agreed with the fact that a PowerShell module manager is needed!

If you look to psget the boys Mike Chaliy, Jason Stangroome, Mark Robert Johnson and others has done a very very good Job.

See: https://github.com/psget/psget

So I think these guys are the right ones to talk to. I am only a consumer of this topic no producer ;-)

Jason Sangroom has Presented his: Requirements for a PowerShell module manager

blog.stangroome.com/.../requirements-for-a-powershell-module-manager

Folow the discussion there.

So I have adopted and extended the ideas of Jansons and started to plan my own Project. Please see my vision there:

github.com/.../MoGet-PowerShell-Module-Manager-Home

(Unfortunately I never started this Project)

I have rapt attention how the story will go with PowerShellGet as a Module manger ;-)

Greets Peter Kriegel

Founder member of the European, German speaking, Windows PowerShell Community

http://www.powershell-group.eu/


No comments: