If you haven’t yet used Munki its an excellent open source tool for software/profile deployment
Below is quick guide on how to get up and running on Yosemite Server, full credit to the awesome Github community and OSXDominion along with my own notes đ
Setting Up Munki With OS X Yosemite Server
There are many ways to set up Munki, since itâs just a webserver. TheDemonstration Setup is a great way to get started, but doesnât list the steps for setting up OS X Server. A lot of new Munki admins (or generally new Munki admins) may have an OS X Server they have access to, but not other web servers, so a guide to getting started with the latest version of OS X Server (as of writing time, thatâs Server 4, on Mac OS 10.10.2 Yosemite) may be helpful.
This is all assuming youâve got Server.app set up and running.
If the Websites service in Server.app is running, turn it off first.
The first steps are to create the Munki repo in the location that Server 4 uses to store website data:
mkdir /Library/Server/Web/Data/Sites/Default/repo
mkdir /Library/Server/Web/Data/Sites/Default/repo/catalogs
mkdir /Library/Server/Web/Data/Sites/Default/repo/pkgs
mkdir /Library/Server/Web/Data/Sites/Default/repo/pkgsinfo
mkdir /Library/Server/Web/Data/Sites/Default/repo/manifests
Change permissions to make sure itâs accessible:
chmod -R a+rX /Library/Server/Web/Data/Sites/Default/repo
In the Server.app Websites pane, edit the âServer Websiteâ (port 80) settings:
Next to âRedirectsâ, click âEditâŚâ, and remove the only redirect (which automatically redirects port 80 to port 443 traffic). It should look like this:
Next, click âEdit Advanced Settingsâ and check the box for âAllow folder listingâ (just for now â itâs easier to visually test this way):
Turn the Websites service on.
Open up Safari, navigate to:
http://localhost/repo/
You should see a page like this:
If you can get to this point, youâve done the website setup work. Now you can go to the next section:
https://github.com/munki/munki/wiki/Demonstration-Setup#populating-the-repo
Once youâve populated the repo, you can set up a new manifest called âtest_munki_clientâ. Follow the instructions exactly:
https://github.com/munki/munki/wiki/Demonstration-Setup#creating-a-client-manifest
Go through the Client Configuration section:
https://github.com/munki/munki/wiki/Demonstration-Setup#munki-client-configuration
Here, you need to do two things on your OS X client.
If you are testing this on the OS X Server itself (i.e. you are only using one machine total), do this:
sudo defaults write /Library/Preferences/ManagedInstalls SoftwareRepoURL "http://localhost/repo"
sudo defaults write /Library/Preferences/ManagedInstalls ClientIdentifier "test_munki_client"
If you are testing Munki on a different client machine from the server, do this:
sudo defaults write /Library/Preferences/ManagedInstalls SoftwareRepoURL "http://ip_or_domain_name_of_server/repo"
sudo defaults write /Library/Preferences/ManagedInstalls ClientIdentifier "test_munki_client"
And then finally you can check to see if Munki behaves as youâd expect:
sudo /usr/local/munki/managedsoftwareupdate -vv
Populating the repo
We now have a working Munki repo â but itâs completely empty and not useful at all. So letâs start to populate the repo.
Weâre going to use some tools distributed with munki to import packages into our new Munki repo. Download the current munki installation package at https://github.com/munki/munki/releases/latest.
Install the Munki tools by mounting the disk image and double-clicking the Installer package and installing like any other package. A restart is required after installation.
The tools youâll use as an administrator are available from the command-line, and are installed in /usr/local/munki. This location is not in the standard search path, so youâll need to either add this directory to your search paths, or be sure to type the full path when invoking these tools.
The tool we will use to import packages into the munki repo is called munkiimport. We need to configure it before we can use it â telling it where to find our repo, among other things.
bash-3.2$ /usr/local/munki/munkiimport –configure
Path to munki repo (example: /Volumes/repo): /Users/Shared/munki_repo
Repo fileshare URL (example: afp://munki.example.com/repo):
pkginfo extension (Example: .plist):
pkginfo editor (examples: /usr/bin/vi or TextMate.app): TextMate.app
Default catalog to use (example: testing): testing
We are first asked for the path to the Munki repo, and since we set one up at /Users/Shared/munki_repo, thatâs what we enter.
Next, we are asked for a repo fileshare URL. This is used when the repo is hosted on a remote file server, and this would typically be an afp:// or smb:// URL specifying the share. Since weâre hosting the repo on the local machine, weâll leave this blank.
We are then asked to specify an extension to append to the name of pkginfo files. Some admins prefer â.plistâ, some prefer â.pkginfoâ. Personally, I just leave it blank â Munki doesnât care.
Next, you are asked for an editor to use for the pkginfo files. If you like command-line editors, you can specify /usr/bin/vi or /usr/bin/emacs for example. If you, like me, prefer GUI text editors, you can specify a GUI text editor application by name (but be sure to include the â.appâ extension). I picked TextMate.app, but you could choose TextWrangler.app, BBEdit.app, or even TextEdit.app.
Finally, you are asked for the default catalog new packages/pkginfo should be added to. We’ll use a “testing” catalog for this.
Further reading here
