Here's another one for the list:
git://git.puppetmanaged.org/puppet/webserver
I've adapted mine from this and as soon as I can get it on github, I will.
Isaac
On 5/12/10 3:22 PM, Al @ Lab42 wrote:
http://github.com/camptocamp/puppet-apache
http://github.com/wesabe/puppet-apache2
http://github.com/puppet-modules/puppet-apache
http://github.com/simpsonjulian/puppet-apache-ubuntu
http://github.com/ohlol/puppet-apache
or the one athttps://labs.riseup.net/code/projects/shared-apache
For sake of completeness I'd add my own module to the list:
http://git.example42.com/?p=example42modules/.git;a=tree;f=apache
It's not the most complete or evoluted of the bunch but it has its own
points, IMHO.
In any case what I find most important is to define a common naming
for defines that create virtualhosts and general .conf files so that,
whatever the apache module used, there's a common way to manage its
configuration's fragments.
Apache is the typical module that is often referenced by other
modules, right in the definition of a configuration piece that
provides the web access information for an application.
Since I'm almost convinced that people will keep on doing their own
apache modules and there will hardlly be a monstre module good for
every use (I personally find, for example, totally unfit to debianize
the apache setup on a not debian breed: IMHO a puppet module should
strictly follow the OS guidelines, directory's structure and
practices) I would concentrate the efforts in defining "common
interfaces" so that in an application module I can use always the same
syntax to manage its apache configuration file.
my2c
al
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
