You are running a Simple Chocolatey Package Repository v0.3.0.0
View your packages (Atom-based feed, will show up differently in different browsers. Some will show it as raw XML, while others will understand the contents and render it in a nicely formatted structure. Depending on your browser, there may be extensions that can help with the rendering of the content).
To interact with this repository, you will be using Chocolatey from client machines.
Information
Querying / Installing Packages
Add the following URL to the list of Chocolatey sources :
https://chocolatey.kubeshop.io/chocolatey
Example: choco source add --name=internal_machine --source=https://chocolatey.kubeshop.io/chocolatey
For more examples and switches, please see the source command .
To add authentication, please see additional instructions ("Administrator Information" section) when you connect to this repo from localhost.
Adding/Pushing Packages
To add the package push API key to the client machines you use for packaging, use the following:
choco apikey --source="https://chocolatey.kubeshop.io/chocolatey" --api-key={apikey}
Use the command below to push packages to this repository :
choco push [{package file}] --source https://chocolatey.kubeshop.io/chocolatey [--api-key={apikey}]
Installing Chocolatey On Client Machines
Note the url used here is different from the url the scripts use on the Install page of https://chocolatey.org.
Check the official install documentation page for requirements, etc.
Choose PowerShell.exe, cmd.exe, or to install with an integrated tool like Boxstarter, Ansible, Chef, Puppet, SCCM, etc.
PowerShell.exe - copy and paste the following into the shell and press enter:
Set-ExecutionPolicy Bypass -Scope Process -Force; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.kubeshop.io/install.ps1'))
Cmd.exe - copy and paste the following into cmd.exe and press enter:
@"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.kubeshop.io/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"
Integrations:
When using Infrastructure Management Tools , ensure you've put a chocolatey.nupkg on this repository.
Ansible - use win_chocolatey module . Support for internal/offline install was added in the 2.7 release. Set the module option source
to https://chocolatey.kubeshop.io/chocolatey. Once Chocolatey is installed, win_chocolatey_source_module can be used to configure this server as a package source.
Boxstarter - installing Chocolatey is built-in to Boxstarter.
Chef - use Chocolatey cookbook to ensure installation. Go to Chocolatey Search and find <content type="application/zip" />
- copy the entire src url. Then set the attribute node['chocolatey']['install_vars']['chocolateyDownloadUrl']
to that value.
PowerShell DSC - use cChoco DSC resource . Set cChocoInstaller
's ChocoInstallScriptUrl
to https://chocolatey.kubeshop.io/install.ps1
Puppet - use puppetlabs/chocolatey . Go to Chocolatey Search and find <content type="application/zip" />
- copy the entire src url. That's what you will provide to class {'chocolatey': chocolatey_download_url }
. See specific instructions at Install with Puppet for examples.
Salt - use Salt.Modules.Chocolatey . The bootstrap doesn't support offline install - subscribe, vote, and comment on Salt issue #45969 for progress. There is a workaround available.
Others - use install script url: https://chocolatey.kubeshop.io/install.ps1
Based on NuGet.Server v3.0.2