Skip to content

jmaaks/macos-setup

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MacOS-Setup

MacOS-Setup is a shell script and Ansible playbook to set up a fresh macOS environment. It installs and configures most of the software I use on my Mac.

It can be run multiple times on the same machine safely. It installs, upgrades, or skips packages based on what is already installed on the machine.

To kick off this process, simply start the install.sh script with:

sh -c "$(curl -fsSL https://raw.githubusercontent.com/jmaaks/macos-setup/master/install.sh)"

Requirements

I've tested it on:

  • macOS High Sierra (10.13.4)

Bootstrap Script: install.sh

The install.sh script bootstraps a new macOS installation by performing the following tasks:

  • Install Xcode Command Line Developer Tools
  • Install Homebrew
  • Install Pip
  • Add Python 2.7 user bin directory to the PATH variable (for pip)
  • Install Ansible via pip
  • Clone this repository locally
  • Call playbook.yml via Ansible to continue the installation/configuration process

TO-DO for install.sh

  • Verify sudo keep-alive is working
  • See whether pip installation needed (since now included in Python by default)

Ansible playbook: playbook.yml

This is the main Ansible installation/configuration script. It contains the following sections:

  • hosts: all
  • vars:
    • applications: the list of all applications that should be installed (using "brew cask install")
    • brew_taps: additional Homebrew repositories
    • brew_utils:
    • docitems_to_remove: list of apps to remove from the Mac dock
    • docitems_to_persist: list of apps to keep in Mac dock
    • home: user home directory
  • tasks:
    • Check Homebrew is installed
    • Install Homebrew
    • Install required Homebrew taps
    • Install libraries/utils with Homebrew
    • Cleanup after brewing
    • Check for installed apps (casks)
    • Install apps with brew-cask
    • Remove items from Mac dock (using dockutil)
    • Add items to dock (if needed)
    • Fix dock item order
    • Configure system settings (via scripts/system_settings.sh)

If you want to add/remove to the list of apps/utils installed, simple edit playbook.yml and re-run the bootstrap script.

You can do this as many times as you like and re-run the ansible-playbook command. Ansible is smart enough to skip installed apps, so subsequent runs are super fast.

TO-DO for playbook.yml

  • Find a fix for installing VirtualBox via Homebrew without GUI permission granting
  • Modularize playbook contents

Included Applications / Configuration

Applications

Apps installed with Homebrew Cask:

Packages/Utilities

Things installed with Homebrew:

  • autoconf

There are several more utils listed in the playbook.yml - simply uncomment them to include them in your install.

System Settings

It also installs a few useful system preferences/settings/tweaks with a toned-down verson of Matt Mueller's OSX-for Hackers script.

It does some reasonably gnarly stuff e.g.

  • hide spotlight icon
  • disable app Gate Keeper
  • change stand-by delay from 1hr to 12hrs.
  • Set trackpad tracking rate.
  • Set mouse tracking rate.
  • and lots more...

so you need read it very carefully first. (see scripts/system_settings.sh)

TODO: moar sick settings with https://github.com/ryanmaclean/OSX-Post-Install-Script

User Preferences

It then syncs your user prefs with dotfiles+rcm

It grabs the thoughttbot/dotfiles repo, saves it in ~/src/thoughtbot/dotfiles and symlinks it to ~/dotfiles.

It then grabs glennr/dotfiles repo, saves it in ~/src/glennr/dotfiles and symlinks it to ~/dotfiles-local

You probably want to change the dotfile_repo_username variable to match your github username :-)

It then runs rcup to initialize your dotfiles.

MacStore Apps (WIP)

These apps only available via the App Store: *

mas from Homebrew will install Mac App Store apps

Application Settings (WIP)

Keep your application settings in sync.

TODO: Add Mackup task

Other

Development

You shouldn't wipe your entire workstation and start from scratch just to test changes to the playbook.

Instead, you can follow theses instructions for how to build a Mac OS X VirtualBox VM, on which you can continually run and re-run this playbook to test changes and make sure things work correctly.

Approach

We've tested it using an OSX 10.10 Vagrant/Virtualbox VM for developing & testing the Ansible scripts.

Simply spin up the Yosemite box in a VM, and have vagrant kick off the laptop setup.

Whats included?

Nada. Well not much. The whole point is to test the process of getting our OSX dev machines from zero to hero.

The Vagrant box we use is a clean-ish install of OSX. However the setup notes above uses Packer, which installs Xcode CLI tools. This can't be automated in an actual test run, and needs user intervention to install.

Test Setup

  1. Get Homebrew Cask

     brew install caskroom/cask/brew-cask
    
  2. Install Vagrant

     brew cask install --appdir="/Applications" vagrant
    
  3. Install VirtualBox;

     brew cask install --appdir="/Applications" virtualbox
    
  4. cd into this project directory;

  5. Run

     vagrant init http://files.dryga.com/boxes/osx-yosemite-10.10.3.0.box;
    
  6. The Vagrantfile should be ready as soon as Vagrant downloads the box;

  7. Start VM

     vagrant up
    

Notes

  • VirtualBox doesn't have Guest additions for Mac OS X, so you can't have shared folders. Instead you can use normal network shared folders.

  • If you are rolling your own box with the OSX VM template, this is the Packer config;

    ```
    packer build \
      -var iso_checksum=aaaabbbbbbcccccccdddddddddd \
      -var iso_url=../out/OSX_InstallESD_10.10.4_14E46.dmg \
      -var update_system=0 \
      -var autologin=true \
      template.json
    ```
    

Author

Jeff Maaks, 2018.

Credits

This project is based off the work of the following folks;

See also:

  • Battleschool is a more general solution than what I've built here. (It may be a better option if you don't want to fork this repo and hack it for your own workstation...).
  • osxc is another more general solution, set up so you can fork the xc-custom repo and get your own local environment bootstrapped quickly.
  • MWGriffin/ansible-playbooks was the original inspiration for this repository, but this project has since been completely rewritten.

Packages

No packages published

Languages

  • Shell 100.0%