mac-dev-playbook VS direnv

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 also made the export diff configurable, motivated by this post: https://github.com/direnv/direnv/pull/1233

Nice.

For years I've been using [direnv](https://direnv.net/) for this, setting environment variables which git picks up. This looks like a more feature complete equivalent, although to be honest I only really need switching of committer email and the SSH key used.

Direnv, for the uninitiated, loads and unloads environment variables when directories are entered and exited. Under every project folder there is a `$PROJ_DIR/.envrc` which contains:

buffer-env: A pure-Elisp version of the direnv utility. Useful to make Emacs aware of Python virtualenvs (which, judging by the questions posted here, is unfortunately still a complication for a lot of people). Similar to (and inspired by) envrc, but doesn't require the direnv program.

You can look at direnv to see this in action as they wrote shell hooks that get loaded into the shell profile and are executed on every prompt. https://direnv.net/

Yes, most Nix users employ https://direnv.net or the equivalent for your IDE of choice. Emacs for instance has https://github.com/purcell/envrc which set per-buffer variables.

The more applications I write, the more I tend to avoid typical config files in favor of using direnv [0] to set environment variables.

[0] https://direnv.net/