A kick ass tool for creating AutoPkg recipes.
Recipe Robot is the easiest way to create new AutoPkg recipes for simple Mac apps. It consists of two components:
A Python script that takes various types of input and automatically outputs AutoPkg recipes.
This two-pronged approach allows AutoPkg novices to easily create recipes that follow community-accepted guidelines, and still provides a command-line tool for more advanced AutoPkg users. Also, using Python for program logic fosters community contribution to this project.
The native Recipe Robot app requires macOS 10.13 or higher, but the Python script should work on previous versions of macOS.
You also need AutoPkg 2.0.2 or later installed, which includes the version of Python 3 Recipe Robot depends on.
- Your desired recipe types - Your preferred recipe identifier (e.g. com.github.your_name_here) - Your recipe output location
Then click Good to Go.
Now you're ready to build some recipes! Drag in an app that you want to create recipes for.
IMPORTANT: The Recipe Robot app currently works best with apps that have a Sparkle feed, and for which there are no existing AutoPkg recipes.
You'll see some activity while Recipe Robot processes the app. If no errors are encountered, click Reveal Recipes to see the finished product.
Here's what the whole process looks like:
Recipe Robot's Mac app is designed to be easy to use, but it's the command-line Python script that contains the real horsepower. To use it:
ln -s "/Applications/Recipe Robot.app/Contents/Resources/scripts/recipe-robot" /usr/local/bin/recipe-robot
For, you can use one of several types of information:
The first time Recipe Robot runs, you'll be prompted for some information. On subsequent runs, you can use the
--configargument to force this prompt to return.
Here's what the Recipe Robot command-line script looks like in action. The command I used was:
/Applications/Recipe\ Robot.app/Contents/Resources/scripts/recipe-robot --verbose /Applications/Mountee.app
This animation hasn't been sped up. Recipe Robot really is that fast! Most of the time, the longest part of the process is the app download, which will depend on your individual internet connection speed.
I always use
--verbosemode. It's fun to see the details, and it proves very useful for troubleshooting.
I've produced a series of video tutorials to demonstrate various features of Recipe Robot.
Also see the Tips section below for more timesavers.
My goal is not to make Recipe Robot generate perfect recipes 100% of the time. There will be apps that Recipe Robot may not be able to generate recipes for, and some recipe types are more complex to build than others. I hope Recipe Robot will make the process of writing recipes for simple apps much faster and more consistent. The recipes created by Recipe Robot should serve as a platform that you can customize before using and sharing.
You may still need to make a recipe the old fashioned way, if the Robot comes up empty.
By default, Recipe Robot does not generate recipes for an app if any AutoPkg recipes already exist for that app. This is a design choice we made after careful consideration, for two reasons:
It's difficult to parse a ParentRecipe and determine exactly which processors will be needed and which file paths we can rely on. Your brain is still the best tool for that.
Many AutoPkg recipe authors put a lot of work into creating and maintaining their recipes, and it's important that we respect that by refraining from uploading duplicate recipes to GitHub.
You can override this etiquette, but please only post a duplicate set of recipes to GitHub if they meet these guidelines:
Each time Recipe Robot produces a batch of recipes for you, I suggest you check a few things before letting the recipes loose in the wild:
The filename of the recipe and the
NAMEinput variable are determined by the name of the app itself. Many apps are suffixed with a version number (e.g. "Delicious Library 3"), and that version number may not be desirable in all cases. You may need to remove the version number from the filename, recipe identifiers, and
Recipe Robot doesn't currently know the difference between an app installer and a bona fide app. Therefore, certain apps may produce recipes that simply install the app's installer instead of the app itself. When this happens, it's usually pretty obvious because you'll end up with a set of recipes called, for example,
ChronoSync Installer.___.recipeinstead of
ChronoSync.___.recipe. The download recipe is probably usable, but the others will need significant customization.
Recipe Robot does its best at determining an app's description for use in Munki and JSS recipes. But it's far from perfect, and it will surprise you with false positives! Always double-check the description before running Munki and JSS recipes or uploading them to GitHub.
It's fine to use a version-specific URL as input, but be careful that it doesn't result in download recipes that depend upon it. Such recipes will not serve the purpose of downloading the latest version using AutoPkg.
You may need to try again with a different URL (preferably one like
http://downloads.pretendco.com/Foo.zipwhich doesn't point to a specific version).
Or you may want to explore using URLTextSearcher to determine the latest URL by inspecting the source of the developer's download page.
If you provide Recipe Robot with the path to an app that came from the Mac App Store, it will create an override for use with Nick McSpadden's AppStoreApp recipes. Please see the details in his README for requirements necessary to use these overrides.
If all you need to do is to build a JSS recipe that uses an existing pkg recipe as its parent, you may want to check out JSSRecipeCreator, which can build both conventional (*.jss.recipe) and "package only" (*.jss-upload.recipe) type recipes. Recipe Robot is not designed to create child recipes for existing parent recipes, although with some tweaking you can certainly use it that way.
1. Provide the app itself as input to Recipe Robot. 2. If that doesn't work, go to the developer's website and see if they provide a static download link (usually ends with .zip or .dmg). Try using that with the Recipe Robot [script](#python-script-usage). 3. If that still doesn't work, maybe the app has a GitHub or SourceForge project page? Try providing that to the Recipe Robot [script](#python-script-usage). 4. Still no luck? Write a recipe from scratch like the good old days. It builds character.
Run again with
--verbosewhen errors occur, and you'll usually see why. It's often because Recipe Robot couldn't determine how to download the app.
If you get Python exceptions while using Recipe Robot, I invite you to create an issue on GitHub so I can track the problem. Include full traceback plus whatever input (URL, path, etc) you provided when you ran Recipe Robot.
The best way to get in touch is by opening an issue on GitHub.