# PowerShell Gallery alternatives **URL:** \ **Category:** PowerShell Help\ **Created:** [April 21, 2016, 1:32am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273 "2016-04-21T01:32:32Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [April 21, 2016, 1:32am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/1 "2016-04-21T01:32:32Z")
Just wondering what the best way would be to acquire modules and DSC resources in an environment where downloading via cmdlets (save-module, etc.) is blocked. I use the gallery at home, but the DoD seems to have this blocked, so it isn’t accessible to me at work where I need it most. I know I can get some things from the Technet Script Center ([https://gallery.technet.microsoft.com/scriptcenter](https://gallery.technet.microsoft.com/scriptcenter)), but given the popularity of the PowerShell Gallery, I doubt people will be keeping the script center up to date. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [April 21, 2016, 1:37am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/2 "2016-04-21T01:37:00Z")
I see the PowerShell team has their resources up on GiHub. > **[PowerShell Team](https://github.com/powershell/)** > > https://microsoft.com/powershell. PowerShell Team has 100 repositories available. Follow their code on GitHub. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [April 21, 2016, 1:44am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/3 "2016-04-21T01:44:44Z")
You can set up your own private NuGet server that acts just like the PowerShell Gallery. Most recently, they’ve set up this repo, though it’s in Preview status: [GitHub - PowerShell/PSPrivateGallery: DSC Resources and Configurations to deploy and manage Private PowerShell Gallery](https://github.com/PowerShell/PSPrivateGallery) . There’s an older blog post here as well: [Setting up an Internal PowerShellGet Repository - PowerShell Team](https://blogs.msdn.microsoft.com/powershell/2014/05/20/setting-up-an-internal-powershellget-repository/) ---
**Author:** ![donj](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/donj/32/137_2.png) [@donj](https://forums.powershell.org/u/donj)\ **Post date:** [April 21, 2016, 2:05am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/4 "2016-04-21T02:05:23Z")
GitHub isn’t the right spot; that’s the developer branch of the code, not necessarily the stable release. Dave’s right - an internal repo (which will be easy to set up, soon), and you can go out-of-office to acquire content, bring that content in, and load it into your private repo. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [April 21, 2016, 3:25am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/5 "2016-04-21T03:25:27Z")
Thanks guys, I have played around with the preview of the private gallery. We were looking at using this for sharing some of internal scripts/modules. Was hoping there might be an option that would not require me to get content off site, but it seems like that might be a dead end. ---
**Author:** ![donj](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/donj/32/137_2.png) [@donj](https://forums.powershell.org/u/donj)\ **Post date:** [April 21, 2016, 4:14am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/6 "2016-04-21T04:14:43Z")
Well, thing is, you guys aren’t blocking the cmdlets, you’re blocking sites, proabbly via your firewall or proxy. So there might be galleries out there that people have set up, which you’re not blocking, but only you’d be able to find out what those are, and they’d likely not include the same modules as the main PSGallery. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [April 21, 2016, 5:58am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/7 "2016-04-21T05:58:15Z")
Right, web access for all elevated accounts is blocked via proxy. So the cmdlets are a no go, unless the source is internal. Was looking to download certain resources the old school way - via the browser. I can get to [PowerShellGallery.com](http://PowerShellGallery.com), but there doesn’t appear to be a conventional download link, and the script center seems to be nearly a year out of date for most things. I appreciate your help, but it seems that my only real option (as usual) is to download at home and sneaker-net it over. ---
**Author:** ![donj](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/donj/32/137_2.png) [@donj](https://forums.powershell.org/u/donj)\ **Post date:** [April 21, 2016, 6:16am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/8 "2016-04-21T06:16:35Z")
What about using a non-elevated account just to do the download, with the destination being some internal repo? I could even see a script, run under non-elev privileges, to “mirror” PSGallery on a weekly basis or whatever. ---
**Author:** ![henry-buckle](https://avatars.discourse-cdn.com/v4/letter/h/f0a364/32.png) [@henry-buckle](https://forums.powershell.org/u/henry-buckle)\ **Post date:** [April 21, 2016, 6:51am UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/9 "2016-04-21T06:51:29Z")
If you just want to download the .nupkg file from [powershellgallery.com](http://powershellgallery.com) using the browser then the link format is as follows [https://www.powershellgallery.com/api/v2/package/PackageName/Version](https://www.powershellgallery.com/api/v2/package/PackageName/Version) e.g. [https://www.powershellgallery.com/api/v2/package/ISESteroids/2.4.0.44](https://www.powershellgallery.com/api/v2/package/ISESteroids/2.4.0.44) You can then install it using Install-Package, or upload it to an internal repository ---
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [April 21, 2016, 11:29pm UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/10 "2016-04-21T23:29:57Z")
Thanks Henry, that is exactly what I was looking for. That works. ---
**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\ **Post date:** [May 16, 2024, 8:41pm UTC](https://forums.powershell.org/t/powershell-gallery-alternatives/6273/11 "2024-05-16T20:41:33Z")