mac-dev-playbook VS formation

To get your Linux ready to use after a fresh install you might have an Ansible playbook to get the system ready to go with all the tools you need.

Not public. But you can search YouTube for geerlingguy and Ansible Mac. I got the idea from him https://github.com/geerlingguy/mac-dev-playbook

This is how I set up my Mac as well; just a local connection. Sets up out of box Mac in about 15 minutes and I can keep my two Mac's configs in perfect sync: https://github.com/geerlingguy/mac-dev-playbook

One way I have seen is to use Ansible and a playbook - Jeff Geerling does this here but that's a bit OTT for me.

Jeff Geerling has a Mac Dev PlayBook repo that is pretty close to how I would build my system.

There is, I use this with some of my own customizations https://github.com/geerlingguy/mac-dev-playbook

If you go down the route of using Ansible, this is a very complete script for Mac OS. Even if you don't use it, you can see how many useful apps can be installed (mac-dev-playbook)[https://github.com/geerlingguy/mac-dev-playbook]

If you go down the route of using Ansible, this is a very complete tool for Mac OS. Even if you don't use it, you can see how many useful apps can be installed mac-dev-playbook And if Ansible if just too much, try this simple way to code, document, and replay bits of your installation scripts with this tool I wrote recently and use to deploy systems daily. markdown_exec

I symlink a few files in place via Dropbox, but have most of my local configs in a dot files repo: https://github.com/geerlingguy/dotfiles

Then for more systemwide configuration, I have an Ansible playbook I run every now and then (configures apps, dock item order, etc): https://github.com/geerlingguy/mac-dev-playbook

Unlike Mina Markham, I choose not to automate my setup because I only do it about once a year and I want the ability to make conscious changes each time.