mac-dev-playbook VS rcm

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

Are your per-machine branches mostly distinct, or do they share a lot?

I use https://github.com/thoughtbot/rcm and I find my dotfiles share _quite a bit_ in some respects (e.g. neovim config) but are drastically different in others (SSH config as one example) -- keeping things synced _across_ branches sounds very difficult. rcm handles this well, without branches, IMO.

I use https://github.com/thoughtbot/rcm, which works smoothly and includes support for host-specific files

I use thoughtbot/rcm to handle my github dotfiles. Super short version after installing, mkdir ~/.dotfiles Then go through your home directory (ie. ~/ ) and mkrc .bashrc and then do the same for any other files you plan on tweaking or have custom settings for. Most of these with be in ~/.config/ but some will be in ~/ . (ie. mkrc ~/.bashrc for your bash settings and aliases)

Prior to catching the Nix brainworms and switching to home-manager, I mostly used thoughtbot/rcm.

Personally I like (and use) rcm. Everything is still in a git repository, but has more features that work well for sharing across multiple machines.

Check out https://github.com/thoughtbot/rcm

I use rcm. It assumes you keep a separate (potentially version-controlled) folder at ~/.dotfiles or similar, and it provides a suite of tools for managing the symlinks.

https://github.com/thoughtbot/rcm

currently I am managing my dotfiles with rcm (ran by ansible). This approach served me well over the years but recently I stumpled over chezmoi.

Setup a Github/Gitlab account and find a dotfile manager you like (I'm using RCM - it can do more than I actually use it for).