This repository is a collection of recipes for use with AutoPkg. This collection represents AutoPkg recipes that the Client Platform Engineering (CPE) team has authored.
You can see other projects from the CPE team at the IT-CPE GitHub repo.
Clone the repo using autopkg repo-add or git clone:
autopkg repo-add https://github.com/facebook/Recipes-for-AutoPkg.git
or
git clone https://github.com/facebook/Recipes-for-AutoPkg.git ~/Library/AutoPkg/RecipeRepos/com.github.autopkg.facebook-recipes
Then run any of the recipes with autopkg run.
The Android Native Development Kit recipes a custom processor: "AndroidNDKVersioner".
There are two versions of note for the NDK: the release number, which is arbitrarily determined by Google, and the version number inside the download. Release number is determined naively by parsing the download file name itself. The version is parsed by looking in the "source.properties" file for the value of "Pkg.Version".
Unlike prior versions of this recipe, this is now idempotent.
The Android Software Development Kit recipe uses a number of custom processors to determine versioning and URLs.
This recipe parses two XML files that Google uses to inform the URLs, versions, and names of all packages related to the SDK. The Android SDK installer, which is a Java app, can download all of these manually (and uses those two XML URLs to figure out what to download).
This is a minimal set of packages necessary to start developing with the Android SDK. It is not the complete SDK.
The Android SDK requires Java 7 in order to function.
BlueJeans is a video conferencing tool. Previously, BlueJeans was only available as browser plugins, but they now offer desktop applications for Windows and OS X.
This recipe will download the BlueJeans installer package and create a straightforward app-dmg that copies the BlueJeans.app into /Applications.
DbVisualizer is a database visualizer tool. The software has a Free version, and can be upgraded into Pro version with proper licensing.
Duo is a 2 factor authentication system. This recipe downloads the latest version of Duo Unix and compiles it to be placed into /usr/local/bin/ rather than /usr/bin/, for compatibility with 10.11 El Capitan.
Since this is a standard configure / make / make install Linux installer, the custom processors provided here will create a tiny sandbox to do the custom install into the AutoPkg cache, so it won't affect your current system.
IntelliJ IDEA is a lightweight developer IDE for Java, Groovy, and Scala.
This recipe contains a custom URL provider, "IntellijURLProvider" that searches their versioning API for the latest download.
This recipe is more of a proof of concept than a usable tool for others. This recipe serves as an example for a way to take an unversionable binary file, such as a large movie file, and create a versionable item that Munki can handle.
This particular example uses a custom processor "DateVersioner" that simply uses the current date and time to name the item, and set a version for Munki importing.
Since the version is not deterministic and not repeatable unless you change the system clock to go back in time, this recipe is not idempotent. It should be run manually whenever the source media file is updated.
The Mobile Shell, known as "Mosh", is a remote terminal application ideal for certain network conditions and environments.
Mosh can be obtained via GitHub and built from source, installed via Homebrew, or downloaded as a prebuilt package. This recipe set provides downloads for GitHub releases as well as the prebuilt package hosted on the website.
Two custom processors are included, "FBGitHubReleasesInfoProvider" and "Mosh Versioner".
Versioning is accomplished with the custom processor by naively looking at the package name, which is fragile and dependent on the developers maintaining consistency with filenames.
The "FBGitHubReleasesInfoProvider" is nearly identical to the AutoPkg GitHubReleasesInfoProvider processor, but contains some additional logic to parse the correct version, since the developers have been listing the release version as "mosh-1.2.x".
SQLDeveloper is an integrated development environment from Oracle that makes it easier to work with Oracle Databases and database applications.
Unfortunately, the software is a native .app wrapped around a Java app, and the native .app version is static and does not change with updates. A custom versioning processor looks for a file inside the Java core that thankfully is updated with new builds when new versions are released.
VMWare Fusion needs no introduction. This recipe follows the instructions on creating a mass-deployment package that is pre-serialized.
The parent recipe for this is in Justin Rummel's VMware Fusion recipe set. You must add Justin Rummel's recipes to your search directories before you can use this recipe:
autopkg repo-add justinrummel-recipes
To use this recipe, you must, at a bare minimum, create an override and replace the license key with your own. The deploy.ini file contents are an input variable, so you can place in your own settings as you see fit.
Though this recipe does include both .pkg and .munki variants, the .pkg recipe only creates a bundle package, not a flat package, and therefore will need to be put into a DMG / archive of some sort to be used with other deployment mechanisms (JSS, Absolute, etc.).
Facebook also provides a number of Shared Processors that can be used in multiple processors.
Facebook's common convention for custom processors is to bundle together recipe-specific tools with the recipe itself - such as unique Versioners, URL providers, etc. Some processors serve useful purposes for many recipes (such as rsync), and therefore make more sense to be shared in a common location.
These shared processors can be referred to by using the stub recipe identifier com.facebook.autopkg.shared:
<dict>
<key>Processor</key>
<string>com.facebook.autopkg.shared/SubDirectoryList</string>
<key>Comment</key>
<string>Get list of folder contents</string>
<key>Arguments</key>
<dict>
<key>root_path</key>
<string>%RECIPE_CACHE_DIR%/unpack</string>
</dict>
</dict>
See the README inside the Shared_Processors directory for more details about the provided processors.