How do I install Chocolatey packages offline?

Question

I am trying to automate to set up a developer machine software installation. Chocolatey is good to install packages when you connected to the Internet. Is there a way to install packages offline?

I just want to put all the packages in a shared network folder and use that packages to install. If you have an internal application, how do you convert them into a Chocolatey package?

Solution 1

Caching Downloads - Not Deterministic

While there are ways to set the original nupkg (with the version on it, not the one in the packages directory - use download from left side of packages page on the Chocolatey community package repository) and preset the downloaded binaries into the cache folder, it's not always deterministic that it will work. You can also override the cache location, so that the folder is somewhere not in TEMP. See choco config, choco config -h and choco config set cacheLocation c:\some\location to do this.

Create Your Own Packages - Better

For packages you need offline, you have the ability to manage your own packages and you can embed software right into the package. This is desired when you want to manage software offline as most things on the community repository are subject to copyright law and distribution rights (why they don't simply have the software they represent embedded).

Creating and working with your own packages is very secure, but it does tend to take up time. If you are doing this for yourself, then it could override any time-savings you get as a consumer using Chocolatey and the community repository.

For organizations, we've developed Package Builder, which creates full software deployments (packages) in 5-10 seconds. It can also create packages right out of existing installed software (Programs and Features) in under 60 seconds! Read more about Package Builder.

Internalized Packages - Best

The best thing you can do here is a process called internalizing, where you download and extract the package, download all of the resources and embed them in the package (or put them somewhere local), edit the scripts to use those embedded/local resources and recompile the package.

This allows you to take advantage of existing package logic without the issue of the internet.

For more details see Manually Internalizing Packages and Package Internalizer - Automatically Internalize Packages.

Organization Use of Chocolatey

Most organizations using Chocolatey are doing some combination of creating packages and internalizing packages, because they need reliability and absolute trust and control over those packages when being used in production scenarios.

Solution 2

I've created a project named ChocolateStore that automates the process of copying a Chocolatey package from an online source and making the package available for offline use.

You can view the source here: https://github.com/BahKoo/ChocolateStore

Solution 3

Chocolatey’s documentation may answer the first part of the question with this: "How To Host Your Own [Private/Internal/Public] Package Repository Server (aka Package Feed)"

It explains three types of package repositories which enable you to provide packages in your LAN/intranet or through shared volumes:

1. Folder/UNC share
2. Simple server
3. Package gallery

The second part of the question could be answered with Chocolatey’s documentation about recompiling packages. The title sounds more complicated than it really is and could just have been "How to make an existing package local", and I think what is described there can be applied to what the question’s author calls "internal applications" (I guess he means programs aka .exe files which are not available on any public feed), too.

Solution 4

So, I have created a Nullsoft installer that needed to install Chocolatey packages from an offline computer. These are the overall steps:

1. Download the Chocolatey packages to a temporary directory with:

   NuGet.exe Install some_package_name -OutputDirectory C:\Temp\ChocoPackages -ExcludeVersion
   

2. In the Nullsoft script, add these lines to pick up the download packages:

   nsExec::Exec 'choco feature disable -n=allowGlobalConfirmation'
   

   SetOutPath "${TmpPath}ChocoPackages" File /r "C:\Temp\ChocoPackages*.*"

3. While still in the Nullsoft script, use this command to install a Chocolatey package from the temporary directory that the files were placed at during the install process:

   choco install --Source "${TmpPath}ChocoPackages" ${Name_Of_ChocoPackage} --acceptlicense --yes
   

View more solutions

Comments

[ferventcoder]

Of course you can override the cache location - see choco config and choco config set cacheLocation c:\somewhere