It's Raining Modules
summary
Practical guide to shipping PowerShell modules: compares hosting options (PSGallery, GitHub/GitLab packages, Azure Artifacts, Cloudsmith, Nexus, Artifactory, BaGet, lightweight NuGet server), notes NuGet v3 support required and that older PowerShellGet needs replacement, explains needing to install NuGet provider on clean build agents, warns about dependency caching and access control, recommends SemVer metadata, optional code signing, compiling multiple PS1 files into a single psm1 for performance and safety, and automating releases after tests pass.
AI-written summary · about
chapters (12)
- 0:00PowerShell module distribution
- 3:12What is a module
- 6:05Avoid public distribution
- 8:13Private repository types
- 11:05Self-hosted solutions
- 13:10PowerShellGet limits
- 14:14Module installation best practices
- 15:17Module design best practices
- 17:03Alternatives to PowerShellGet
- 18:05Code signing for security
- 19:08Single vs multiple files
- 20:55Summary
related talks
46mThese Are the Modules You’re Looking For: Packaging and Publishing PowerShell..
50mGet control of you Git: Managing PS module binaries using VSTS CI/CD and...
52mPowerShell Module Design Rules (and When to Bend Them)
01h 45mWriting Award Winning PowerShell Functions and Script Modules
45mGitHub Actions for Fun and Profit
43mPowerShell Tooling
49mStop manually publishing your modules. Automate it in 2 minutes!
52mWrite Modules, Not Scripts