Picking up where we left off with Jenkins, let's look at one possible workflow to get autopkg projects working. Specifically when paired with Munki, this requires a bit more thought, but the Jenkins 'workspace' model and sane use of variables allows us to make one all-purpose script for most contingencies we'd deal with.
Confession time: back when I was a consultant, I didn't always use best practices. I know - that's a loaded phrase anyway, but this wasn't good. My name is Allister Banks, and I set up autopkg to run as root with a launchdaemon.
It’s been a long-standing goal of mine to help people get started making their own recipes for autopkg, which was recently spurred on by revisiting my previously-discussed recipeGenerationUtils.
In a previous post, I showed how to use Munki with Puppet SSL Client certificates in a Docker image. In that example, the Puppetmaster image is set to automatically sign all certificate requests. Good for testing, but not a good idea for production use.
Previously, I showed how you can run Munki in a Docker container. Then, I talked about how to build Munki to use Puppet for SSL certificates. Assuming you've got a running Puppetmaster image (which I talked about building here), let's run the Munki-Puppet image we just built.
Note: this is based on the README for the Munki-SSL docker container. In a previous post, we ran a Docker container serving Munki repo content via Nginx. That works fine, but only serves insecure HTTP content.
This is based on the README I wrote for the macadmins/puppetmaster image. Puppet is an industrial-strength cross-platform configuration management engine.
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.
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.
