Is there a more dynamic way to manage Apache configs?
We have used the apache web server for some time now, and have written many scripts to pull information out of a database and generate virtualhost config files, webdav config files, ssl config files, etc. I am wondering if there is a more dynamic way to interact with apache configs, such that apache might use a database for it's configuration, or put these configs on an NFS share that all the servers in our network can see, or use a configuration management tool like Chef or Puppet to distribute them?
Looking for experiences, ideas, and theories on a better way to manage apache. Any suggestions on a different web server that supports webdav, and is more flexible in it's configuration are welcome as well.