In the previous post, I built a container that serves static files at http://munki/repo using Nginx. Now that we have build the Docker image, let's put it to use. We're going to hook up the Munki image to a data-only container.
Munki is an incredible tool for Mac software deployment, and the setup process is fairly straightfoward - configure a web server, create your repo, run the tools to populate it with software, and configure clients.
UPDATE January 20, 2015 - Some are reporting an opendirectoryd-related fix, featuring the very cool-looking darwinup. Let's hope it makes it into .2, and we're not all chomping at the bit for 10.10.3! People are noticing a symptom, branded LoginLockout (credit @andrewrose), where Yosemite seemingly freezes during startup.
In our last installment, we introduced a solution for syncing large or already compressed files around without strictly commit'ing them to git proper when collaborating on a munki repo. This was by leveraging the git-fat add-on/script, which only relies on python(2.7) and rsync.
Do you work on munki with a team of folks (meaning more than one)? You probably wish you could use MunkiAdmin for everything, but mounting the munki repo over the network may be a poor experience as things grow very large, and as the server world is mostly nix (if you're lucky), running MunkiAdmin on the server itself is out of the picture.
Five years ago, it was not uncommon to see many cabinets full of Xserves fulfilling serving roles in the enterprise. Today those servers are on their last legs and warrant replacement by modern hardware and software design.
So you've gotten ok with scripts, or at least have tasked yourself with sorting through and in some cases slinging around plain text files. You've even heard about this Github thing, maybe you've already made an account, maybe you're even digging in to it more often.
If you're like me, you love autopkg. You don't even want to perform web searches for download links anymore. I'm told there are certain things that can't be automated. But, when I first saw that many recipes could follow roughly the same format, I thought to myself 'we have to go deeper'(BUMMMMMMM!BUMBUM!
Patchoo is here and aims to bring some Munki-esque features and workflow to Casper. We all know that Casper has some gaps around patch deployment. Whilst Casper 9 somewhat improves capabilities there is still no cohesive way for an end user to install 3rd party and Apple Software Updates.
Munki and Puppet have become very popular tools in the last few years, and make a great team for Mac management. While Puppet is inherently secure due to its use of client-certificate based SSL for all communication, most Munki deployments still run over plaintext HTTP.
