On Wednesday, January 30, 2013 7:16:32 AM UTC+11, ashely wrote:
I suspect you are correct about in house apache modules. I also found > the various apache modules on forge or elsewhere did not accomodate our > site's needs. It is a tough problem. > > We ended up building 2 apache modules. the first handles our messy > "inherited" web site configs. I opted to keep the httpd.conf static and > place all the messy stuff into vhost.conf files. These get managed > either by template or static file depending on complexity. This is less > than ideal and very site dependant. We are up to 90+ vhost templates, > one per url. > > In the second version I tried to be more general. I wanted a way for > any given application which needs web frontend to generate a vhost > config within it's own module without having to directly include an > apache class. In the node def I can then include many such webapp > classes in any combination. I then include my apache class which > serves any vhosts configs it finds in /etc/apache/vhost.d or whatever. > I am using exported resourses for the vhost configs, but I probably > don't need to. > > In both versions I keep the httpd.conf static, and put the apache config > complexity into the vhost configs. > Thanks Ashley for your thoughts. I suspect this is what I'll do too. -- 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.
