Fabric is a good example of config management as code. While all the app-specific configs are much easier to do this way, it feels like many other tasks (instal

Fabric is a good example of config management as code. While all the app-specific configs are much easier to do this way, it feels like many other tasks (install packages, create users, etc) could be "outsourced" to some sort of shared recipe. So I guess it depends on how "custom" your deploy and configs are. If you're doing something standard, ansible/chef could be a good fit, less so if there are many tweaks etc. If anyone is interested in pursuing fabric for their config+deploy, check out these libraries of higher-level system functions: https://github.com/sebastien/cuisine https://github.com/sebastien/cuisine or https://github.com/ronnix/fabtools https://github.com/ronnix/fabtools