cuisine

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 or https://github.com/ronnix/fabtools

Also cuisine[0], a more fully featured configuration management tools built on top of Fabric's lower level functions. [0]: https://github.com/sebastien/cuisine

They definitely have, I've been visiting it a lot lately, when I was writing my own deployment script. Also, you need this too: https://github.com/sebastien/cuisine/

There is also cuisine, which brings chef-like functionality to fabric. https://github.com/sebastien/cuisine

Check out cuisine https://github.com/sebastien/cuisine It is a good companion for fabric to handle user creation and package installs. More info after slide 42 here: http://www.slideshare.net/ffunction/fabric-cuisine-and-watch...