# Setting Up Powershell gallery And Nuget gallery
As like [pypi]() for Python, [npm]() for Node.js, we also have [Powershell Gallery]() for Powershell to add some extra Powershell modules, and [Nuget Gallery]() for Powershell to add some extra executables.
## Powershell version
> [!NOTE]
>
> All commands provided here are tested on Windows 10 with Windows Powershell v5.1.
## Configure proxy in Powershell
Both Powershell Gallery et Nuget Gallery can be installed locally that we don't need external Internet access to retrieve the packages from them, but setting up an internal Powershell Gallery or an internal Nuget Gallery is [out of scope of this post](<#set-up-internal-powershell-gallery-or-nuget-gallery>).
To use the [public Powershell Gallery]() or the [public Nuget Gallery](), you must have Internet access. If you're at the office, your computer is probably behind a company proxy to access Internet. If your Internet Explorer's proxy setting has already been configured, you can use the below command to tell Powershell to reuse the same proxy setting :
```
(New-Object -TypeName System.Net.WebClient).Proxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials
# Or batch version by using netsh (need admin privileges) :
netsh winhttp show proxy
netsh winhttp import proxy source=ie
```
I suggest to add the above command in your powershell profile, otherwise you should type it each time you open a new Powershell session.
Your Windows Powershell profile can be found at four locations:
```
$PROFILE | gm | ? membertype -eq noteproperty
```
The output of the above command :
```
# For Windows Powershell :
TypeName:System.String
Name MemberType Definition
---- ---------- ----------
AllUsersAllHosts NoteProperty string AllUsersAllHosts=C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1
AllUsersCurrentHost NoteProperty string AllUsersCurrentHost=C:\Windows\System32\WindowsPowerShell\v1.0\Microsoft.PowerShell_profile.ps1
CurrentUserAllHosts NoteProperty string CurrentUserAllHosts=d:\xiang\Documents\WindowsPowerShell\profile.ps1
CurrentUserCurrentHost NoteProperty string CurrentUserCurrentHost=d:\xiang\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
```
The two CurrentUser profile locations might differ on different computers, all depends on your `MyDocuments` location ( `[Environment]::GetFolderPath("MyDocuments")` ), and if you're using Powershell Core, all the four locations are different than the ones in Windows Powershell. I use usually `CurrentUserAllHost` because the change will only affect my profile, and even if I'm not the admin of the computer, I can still get it work. The profile location can be found at :
```
$PROFILE | % CurrentUserAllHosts
```
Add proxy setting in the end of your `CurrentUserAllHost` powershell profile :
```
Add-Content ($PROFILE | % CurrentUserAllHost) "`n(New-Object -TypeName System.Net.WebClient).Proxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials`n"
```
As a best practice, it would be better to add the above line at the top of your profile.
## Set up Powershell Gallery for Powershell
This is pretty easy for Powershell v5+ :
```
# I add the switch Trusted because I trust all the modules and scripts from Powershell Gallery
Register-PSRepository -Default -InstallationPolicy Trusted
```
For Powershell with version less than v5:
```
Register-PSRepository -Name PSGallery -SourceLocation https://www.powershellgallery.com/api/v2/ -InstallationPolicy Trusted
```
Test :
```
> Get-PSRepository
Name InstallationPolicy SourceLocation
---- ------------------ --------------
PSGallery Trusted https://www.powershellgallery.com/api/v2/
```
## Use Powershell Gallery
```
# Search a module which name is like poshrs*
> find-module poshrs*
Name Version Source Summary
---- ------- ------ -------
PoshRSJob 1.7.4.4 PSGallery Provides an alternative to PSjobs with greater performance and less overhead to run commands in ...
# Install the module without admin privileges
> find-module poshrs* | install-module -Scope CurrentUser
```
## Set up Nuget for Powershell
[Nuget]() is well-known among the Windows developers.
```
# I also add the Trusted switch
Register-PackageSource -Name Nuget -Location "http://www.nuget.org/api/v2" -ProviderName Nuget -Trusted
```
My Nuget client is at v2, so I can only target at Nuget v2 API.
```
> Get-PackageProvider
Name Version DynamicOptions
---- ------- --------------
msi 3.0.0.0 AdditionalArguments
msu 3.0.0.0
NuGet 2.8.5.208 Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag, ...
PowerShellGet 1.0.0.1 PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, In...
Programs 3.0.0.0 IncludeWindowsInstaller, IncludeSystemComponent
```
Test :
```
> Get-PackageSource
Name ProviderName IsTrusted Location
---- ------------ --------- --------
Nuget NuGet True http://www.nuget.org/api/v2
PSGallery PowerShellGet True https://www.powershellgallery.com/api/v2/
```
## Use Nuget
```
# install the latest version of GitForWindows without admin privileges
find-package gitforwindows | install-package -Scope CurrentUser
# install the latest version of Python without admin privileges
find-package python | install-package -Scope CurrentUser
# find the path of Python installation
get-package python | % source
# You need to add manually the package executable path to your USER PATH.
# To get the current USER Path
[System.Environment]::GetEnvironmentVariable('Path', 'User')
# To set the current USER Path
[System.Environment]::SetEnvironmentVariable('Path', $newPathInSingleStringSeparatedByColumn, 'User')
```
> In fact, you can find out from the output of `Get-PackageSource` that `Find-Package` can search the packages and modules in both Nuget Gallery and Powershell Gallery.
## Set up internal Powershell Gallery or Nuget Gallery
Some resources on setting up internal Powershell Gallery and Nuget Gallery:
1. [Setting up an Internal PowerShellGet Repository]()
2. [Powershell: Your first internal PSScript repository]()
3. [PowerShell/PSPrivateGallery]()
4. [Overview of Hosting Your Own NuGet Feeds]()
5. [NuGet/NuGetGallery]()