- #BLOCKBLOCK AUTOPKG RECIPE INSTALL#
- #BLOCKBLOCK AUTOPKG RECIPE ZIP#
- #BLOCKBLOCK AUTOPKG RECIPE DOWNLOAD#
If you make changes then version up in your ist and build again. Run munki-pkg on the command line and build your package. #!/bin/shĭefaults -currentHost write moduleDict -dict moduleName Brooklyn path /System/Library/Screen\ Savers/Brooklyn.saver/ type 0 Example: setting the screensaver you just installed as the default.
#BLOCKBLOCK AUTOPKG RECIPE INSTALL#
Munki will also install apps, run scripts, install profiles, and do many things but packages are useful because we can put files in specific places, such as the main computer level screensaver folder, then run a script to set it as a default.ĭownload munki-pkg and create a working project folder.Ĭreate the folders you need and place your files (payloads) in the right places.Ĭreate your post install script if you need one.
Munki-pkg makes package (PKG) installers, Munki likes pkg installers. Why use munki-pkg? How else do you install stuff using munki, run scripts, and version your testing buildings all in one easy to use application? This is all possible with munki-pkg. Here is an example of installing a screensaver. Use munki-pkg to package up stuff and make your life easier when managing Macs using munki. Posted in Automation, OSX app deployment automation, Tricks And Tips | Tagged Apple, AutoPkg, Deployment, IT, Mac, Munki, opensource, OS X, OSX, sysadmin | 1 Reply Use Munki to install a screensaver Here is an example of newly imported Kyno and Hedge apps in our Munki repo (via Munki Admin GUI).Īdd a display name, choose which catalogs the apps will reside in, and check that the description will help explain what the app is.Įlliot Jordan – Autopkg talk at MacDevOps:YVRĮlliot Jordan – Recipe Robot talk at MacDevOps:YVR Many Thanks to them and the contributors to their projects.Īutopkgr app can send notifications in macOS, emails, or post to your Slack group. Note: Autopkg and Munki can all be run via cli (command line interface) but for this demo we are showing the GUI apps that are there provided by outstanding members of the community. Run them in Terminal or use Autopkgr , a very nice GUI app for automating the collection and scheduling of recipes. You can use your recipes locally with Autopkg. But there are other options: jss, Filewave, or “install” for example.
#BLOCKBLOCK AUTOPKG RECIPE DOWNLOAD#
I chose download and munki because those are what I am using to automate adding apps to my Munki repo. I’ll show an example of this workflow using Recipe Robot and Munki Admin to demonstrate the workflow.ĭrag and and drop the app you want to create your Autopkg recipes. I recently created recipes for two important apps in my media workflow: Kyno and Hedge. Using Recipe Robot we can build Autopkg recipes for most apps then add the recipes to the Autopkg community to enjoy. Using Autopkg recipes to download the latest apps and put them into your Munki repo automatically is an automation love fest, but if your apps don’t have recipes what are you going to do? Manually add your apps to Munki? No way.
But if you’re putting in one off applications into your Munki repo more often than you need to, you need to get those apps into Autopkg.
Using Munki to solve problems makes sense.
#BLOCKBLOCK AUTOPKG RECIPE ZIP#
And really, if you’re going to take the time to download an app from a website, mount a disk image or un-pack a ZIP archive, run an installer, type an admin password, close that installer … then for the love of all that is good just put the app into your Munki repo and be done with it. If more than one person should have it then Munki is definitely the way to automate app deployment. If only one person needs an application then I think about using Munki to deploy that app.
0 kommentar(er)
