mac-dev-playbook VS homeshick

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

I have a work mac, work linux, and home mac. I want the same terminal-based development environment on all of them, but each requires just a little bit of customization.

For example, the .gitconfig for work is different from home (e.g. my username/email). Ditto for my .ssh/config and my shell aliases.

I also use Nix to manage all my tools, and the home-manager configuration is slightly different between mac & linux due to platform support.

I've gone through a few iterations of home-built solutions, including extending homeshick[1], before discovering YADM which implemented everything I had done but better.

[1] https://github.com/andsens/homeshick

I do roughly the same and then manage them with 'homeshick' ( https://github.com/andsens/homeshick )

Have a look at https://github.com/andsens/homeshick project, it makes this workflow much easier.

Homeshick for dotfiles: https://github.com/andsens/homeshick

Docker for Obsidian and Alfred syncing - the three target limit on the free tier is just barely enough for 2 of my own computers and my work laptop.

I've also got a Brewfile for installing the basic tooling on macOS

I also have a "how to set up a new computer/server" document on Notion that I use so I don't forget any steps.

This is the exact reason I use Fish. The only thing I _need_ to get installed on random servers is Fish itself.

No need to install and configure oh-my-$shell or other huge monstrosities. Most of my stuff comes from a simple homeshick[1] sync with a few files in it.

[1] https://github.com/andsens/homeshick