Hi all, I've spent a bit of time today investigating whether or not I can use the Puppet Labs Apache module - https://forge.puppetlabs.com/puppetlabs/apache
I've noted this helpful blog post - http://blog.akquinet.de/2011/11/23/managing-an-apache-server-with-puppet/ However after examining the Apache configuration I've inherited it seems to me that the publicly available module exposes only a fraction of the Apache options in the manifests. E.g. I have inherited several hundred RewriteRules along with RewriteConds, and all that ugliness, non standards paths to files, non standard values passed to prefork and and worker MPM, and so on. In general, looking in templates/httpd.conf.erb file, though, it appears to me that the vast majority of Apache's configuration options can't be controlled by puppet if you use the Apache module. Rather they're hardcoded in this file. This leads me to suspect that most sites must be using Apache modules that were entirely developed in house? Or have most sites just decided that most of Apache's options shouldn't ever be changed from these default settings? Or is there a better Apache module I should look at? Or should I take the initiative and feedback lots and lots of changes to the module? Thanks in advance for feedback. Kind regards, Alex Harvey -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
