cfengine has been around longer, but seems to have negative adoption since puppet became well-known. I know a few people who swear by it, though.
FWIW, at my current startup I use Chef to manage a mid-sized collection of servers (app, load balancers, DBs/replicas, task processors) where the app is written mostly in Python, and it took a ton of pain out of scaling up to deal with a very large paying customer two nights ago.
Puppet has better documentation, but learning either is a bit of a trial and error process I think. You might find Blueprint (https://github.com/devstructure/blueprint) useful to bootstrap (the authors are around in the HN community, I think.)
Blueprint (https://github.com/devstructure/blueprint)
Blueprint I/O (https://github.com/devstructure.com/blueprint-io)
I've used both Puppet and Chef extensively, and they both do the same thing, they just go about it differently. (shameless plug of a blog post I wrote that compared the two: http://redbluemagenta.com/2011/05/21/puppet-vs-chef)
Also, it's almost always about how you approach configuration management - thankfully, with Puppet and Chef, you don't have to manage everything on a system in your CM right away. If you have to manage SSH authorized_key entries and it's getting annoying to do it by hand, then write a Puppet module / Chef cookbook to manage it for you. Then go on to manage /etc/hosts entries, then to deploying packages... you'll hit a point where you can reasonably rebuild a server from scratch without thinking about it.
There's other CM systems out there too: bcfg2, cfengine, etc.
We use Puppet at Disqus (a Python shop). Puppet and Chef are used by pretty much any modern web deployment that didn't already have a system in something more dated (cfengine? custom made?). At least that's the feeling I get.
I can't speak much to Chef but Puppet has great docs. You might just get an intro book for one or the other and dive in.
http://www.usenix.org/publications/login/2010-10/openpdfs/Co...
To help you get started with Cfengine (my specialty):
http://www.cfengine.com/pages/tech http://www.verticalsysadmin.com/cfengine/cfengine_examples.t...
The biggest pain is that the docs were iffy, at least for me. I wasn't the one setting up the servers at work, but when setting up a Chef cookbook for personal use, it was a pain to both learn the DSL and deal with the silliness caused by bugs that hadn't quite made it to release yet. At the end of the day though, its more just experimenting with the tools available until you're comfortable with one.
You can also look into Fabric, which is a Python server automation tool.
Note that the easiest way to start is to not use any of puppet's built-in client-server stuff (puppetd command). Instead run everything like this:
$ git clone $REMOTE_REPO_WITH_MANIFESTS puppet
$ ls
manifests modules
$ sudo puppet --modulepath=modules/ --debug manifests/site.pp
You could use something like fabric if you only have 1-2 servers.[1]http://ericholscher.com/blog/2010/nov/8/building-django-app-...
http://www.usenix.org/publications/login/2011-04/openpdfs/Lu...
I've been looking at Puppet and Chef, but we're not just Rails anymore and I can't imagine that the Ruby world's tools are the only popular ones. I just don't know where to look for how to make an informed choice, how to get started, etc. It feels like there is a large gap in available knowledge between running a couple of processes on a single server and anything I'd trust to some paying customers.