Hey all, I''ve open-sources Digg''s apache module: http://github.com/plathrop/puppet-module-apache I know this isn''t much more advanced than what I''ve seen a lot of people using. Here''s my proposition, though. Let''s get all the disparate "apache" modules out there merged together into One Awesome Module. What do you think? One module to rule them all One module to find them One module to bring them all And via Puppet bind them. --Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop <paul@tertiusfamily.net> wrote:> Hey all, > > I''ve open-sources Digg''s apache module: > http://github.com/plathrop/puppet-module-apache > > I know this isn''t much more advanced than what I''ve seen a lot of > people using. Here''s my proposition, though. Let''s get all the > disparate "apache" modules out there merged together into One Awesome > Module. What do you think? > > One module to rule them all > One module to find them > One module to bring them all > And via Puppet bind them. >+1 -- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I''ll even do the integration work, just link me to your module and I''ll try to integrate its feature set into mine. On Tue, May 11, 2010 at 5:17 PM, Nigel Kersten <nigelk@google.com> wrote:> On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop <paul@tertiusfamily.net> wrote: >> Hey all, >> >> I''ve open-sources Digg''s apache module: >> http://github.com/plathrop/puppet-module-apache >> >> I know this isn''t much more advanced than what I''ve seen a lot of >> people using. Here''s my proposition, though. Let''s get all the >> disparate "apache" modules out there merged together into One Awesome >> Module. What do you think? >> >> One module to rule them all >> One module to find them >> One module to bring them all >> And via Puppet bind them. >> > > +1 > > > -- > nigel > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
+1 Here is another apache module that I wrote: http://github.com/ohadlevy/puppet-foreman/tree/master/apache2/ Thanks, Ohad On Wed, May 12, 2010 at 8:27 AM, Paul Lathrop <paul.lathrop@gmail.com>wrote:> I''ll even do the integration work, just link me to your module and > I''ll try to integrate its feature set into mine. > > On Tue, May 11, 2010 at 5:17 PM, Nigel Kersten <nigelk@google.com> wrote: > > On Tue, May 11, 2010 at 5:15 PM, Paul Lathrop <paul@tertiusfamily.net> > wrote: > >> Hey all, > >> > >> I''ve open-sources Digg''s apache module: > >> http://github.com/plathrop/puppet-module-apache > >> > >> I know this isn''t much more advanced than what I''ve seen a lot of > >> people using. Here''s my proposition, though. Let''s get all the > >> disparate "apache" modules out there merged together into One Awesome > >> Module. What do you think? > >> > >> One module to rule them all > >> One module to find them > >> One module to bring them all > >> And via Puppet bind them. > >> > > > > +1 > > > > > > -- > > nigel > > > > -- > > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Paul These are the ones I know about: 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 Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS+oK2yFa/lDkFHAyAQKQWAf+O8Ga73MCHh357VyjJomeX3D+qXvufrf2 Rdn0t7gPcO355550eOKzPTluF7VxvifKKaeADQktIcnX+o0+VwEYg3Yb198GQMDx e8Vx8MeZs8dq80anVSOko/Zc23U1+R76qQQ0zzRd9S6KzvD5bwlkTaAwtwGM2WE0 kS0R/xx2KA4CRQK/Vtu1u7BCrMoONbXS+5rF+6MCgYerwD+wqOPvX7PH77xdLmZz sFMIinJUkqcaMnZPIWXCxuwAB+abe3WxUGZ7dE1qTgrbt8BEZYuITTRRcXg+kNLO CfMW6sPrCtedfxxW9fyuG/Ko1BVaHlMKpG44cr5LMR0OKm3vFmWgBg==vyFz -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
+1 for this. But let''s not forget the CentOS/RHEL/Fedora folks out there. Minor but key differences in directory structure, permissions, SELinux policies, etc. On 5/11/10 9:56 PM, James Turnbull wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Paul > > These are the ones I know about: > > 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 > > Regards > > James Turnbull > > - -- > Author of: > * Pro Linux System Administration (http://tinyurl.com/linuxadmin) > * Pulling Strings with Puppet (http://tinyurl.com/pupbook) > * Pro Nagios 2.0 (http://tinyurl.com/pronagios) > * Hardening Linux (http://tinyurl.com/hardeninglinux) > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEVAwUBS+oK2yFa/lDkFHAyAQKQWAf+O8Ga73MCHh357VyjJomeX3D+qXvufrf2 > Rdn0t7gPcO355550eOKzPTluF7VxvifKKaeADQktIcnX+o0+VwEYg3Yb198GQMDx > e8Vx8MeZs8dq80anVSOko/Zc23U1+R76qQQ0zzRd9S6KzvD5bwlkTaAwtwGM2WE0 > kS0R/xx2KA4CRQK/Vtu1u7BCrMoONbXS+5rF+6MCgYerwD+wqOPvX7PH77xdLmZz > sFMIinJUkqcaMnZPIWXCxuwAB+abe3WxUGZ7dE1qTgrbt8BEZYuITTRRcXg+kNLO > CfMW6sPrCtedfxxW9fyuG/Ko1BVaHlMKpG44cr5LMR0OKm3vFmWgBg=> =vyFz > -----END PGP SIGNATURE----- > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Paul Lathrop <paul@tertiusfamily.net> writes:> I''ve open-sources Digg''s apache module: > http://github.com/plathrop/puppet-module-apache > > I know this isn''t much more advanced than what I''ve seen a lot of people > using.It looks very much like our internal, not-able-to-release version. The two features we have that you don''t are: * the module enable/disable feature also ships appropriate configuration and installs the appropriate packages for the platform. * apache::conf, which installs a fragment in conf.d/* * apache::listen{,::port80,::port443}, which configures the system to listen on a custom port, and then wraps that in a class for the standard ports.> Here''s my proposition, though. Let''s get all the disparate "apache" modules > out there merged together into One Awesome Module. What do you think?Sounds like a great idea to me, but it is a heck of a lot of work. The most likely "next" feature for us, incidentally, will be to try and extract the parts of a VirtualHost tag that are custom, and the parts that are standard like the header, auth, logging, etc, so that we don''t duplicate those in dozens of different files we install... Daniel -- ✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Did Isaac just volunteer to be the canary for CentOS/RHEL/Fedora? Seriously, I will integrate these various modules, including bringing in any distribution-specific stuff I can find, but I don''t have any experience with the CentOS, etc. family of distributions. Related, though, is the concept that we, as a community, may want to settle on one "right way" to lay out an apache configuration. What I mean is, there ought to be a best practice established by now that we can codify into the module, and lay out the apache configs the same on Linux in general, only different where required to hook into the rest of the system. I think this is one of the few areas where the Debian way is actually really smart. That is probably a different discussion though. --Paul On Tue, May 11, 2010 at 7:13 PM, Isaac Christoffersen <isaac.christoffersen@gmail.com> wrote:> +1 for this. But let''s not forget the CentOS/RHEL/Fedora folks out there. > Minor but key differences in directory structure, permissions, SELinux > policies, etc. > > > On 5/11/10 9:56 PM, James Turnbull wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Paul >> >> These are the ones I know about: >> >> 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 >> >> Regards >> >> James Turnbull >> >> - -- Author of: >> * Pro Linux System Administration (http://tinyurl.com/linuxadmin) >> * Pulling Strings with Puppet (http://tinyurl.com/pupbook) >> * Pro Nagios 2.0 (http://tinyurl.com/pronagios) >> * Hardening Linux (http://tinyurl.com/hardeninglinux) >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.7 (Darwin) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> >> iQEVAwUBS+oK2yFa/lDkFHAyAQKQWAf+O8Ga73MCHh357VyjJomeX3D+qXvufrf2 >> Rdn0t7gPcO355550eOKzPTluF7VxvifKKaeADQktIcnX+o0+VwEYg3Yb198GQMDx >> e8Vx8MeZs8dq80anVSOko/Zc23U1+R76qQQ0zzRd9S6KzvD5bwlkTaAwtwGM2WE0 >> kS0R/xx2KA4CRQK/Vtu1u7BCrMoONbXS+5rF+6MCgYerwD+wqOPvX7PH77xdLmZz >> sFMIinJUkqcaMnZPIWXCxuwAB+abe3WxUGZ7dE1qTgrbt8BEZYuITTRRcXg+kNLO >> CfMW6sPrCtedfxxW9fyuG/Ko1BVaHlMKpG44cr5LMR0OKm3vFmWgBg=>> =vyFz >> -----END PGP SIGNATURE----- >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, May 11, 2010 at 7:33 PM, Daniel Pittman <daniel@rimspace.net> wrote:> Paul Lathrop <paul@tertiusfamily.net> writes: > >> I''ve open-sources Digg''s apache module: >> http://github.com/plathrop/puppet-module-apache >> >> I know this isn''t much more advanced than what I''ve seen a lot of people >> using. > > It looks very much like our internal, not-able-to-release version. The two > features we have that you don''t are:Is it "not able to release yet" or "not ever gonna release"?> * the module enable/disable feature also ships appropriate configuration and > installs the appropriate packages for the platform.Nice, I''d love to add that.> * apache::conf, which installs a fragment in conf.d/*Actually, apache::config in my module does exactly that.> * apache::listen{,::port80,::port443}, which configures the system to listen > on a custom port, and then wraps that in a class for the standard ports.I don''t do it quite the same way, but there is a tunable for the ports: $apache_listen_ports>> Here''s my proposition, though. Let''s get all the disparate "apache" modules >> out there merged together into One Awesome Module. What do you think? > > Sounds like a great idea to me, but it is a heck of a lot of work.Yeah, but I''m going to try anyway.> The most likely "next" feature for us, incidentally, will be to try and > extract the parts of a VirtualHost tag that are custom, and the parts that are > standard like the header, auth, logging, etc, so that we don''t duplicate those > in dozens of different files we install...I love this idea. Will have to see if I can add something to this module. --Paul -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/05/10 12:33 PM, Daniel Pittman wrote:> > * the module enable/disable feature also ships appropriate configuration and > installs the appropriate packages for the platform. >There''s also this that I and Teyo wrote - that manages Apache modules on Debian/Ubuntu. http://github.com/jamtur01/puppet-apache-modules Regards James Turnbull - -- Author of: * Pro Linux System Administration (http://tinyurl.com/linuxadmin) * Pulling Strings with Puppet (http://tinyurl.com/pupbook) * Pro Nagios 2.0 (http://tinyurl.com/pronagios) * Hardening Linux (http://tinyurl.com/hardeninglinux) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBS+ouISFa/lDkFHAyAQJYkAgAkZW6Do8cnVhcpVrVABfjCnjjm1JJzYnw ISjcx1k0KRfKmPLsjxWftn+al2jH6yRCjdESw1AZunBWIXRBzb25VnBMt7KIpV+e Bc1/wp0sUWcznYUEwlRne4OjYLUd9tQkETH/m+K5AR92WNjmjR0leAW6AF3HZkZP 1z8MeSc0jyxewUgixM7vaV3nWKqud1pkhmDF4bcsBpP8cCZFsYHMiO0dK8QO6g78 IeixquwUCNONva7dDNSLgzuaAjU7ltl83cVta4Kq7vZiTFIhPAZguOZxRPv7uAhQ NIvyR99TgfMHTyMsA4Nnpoaxa1F0anoQhxFaJP885QmRci7NzqqdBQ==1JJt -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Paul Lathrop <paul.lathrop@gmail.com> writes:> On Tue, May 11, 2010 at 7:33 PM, Daniel Pittman <daniel@rimspace.net> wrote: >> Paul Lathrop <paul@tertiusfamily.net> writes: >> >>> I''ve open-sources Digg''s apache module: >>> http://github.com/plathrop/puppet-module-apache >>> >>> I know this isn''t much more advanced than what I''ve seen a lot of people >>> using. >> >> It looks very much like our internal, not-able-to-release version. The two >> features we have that you don''t are: > > Is it "not able to release yet" or "not ever gonna release"?I would have to ask my boss; it could be the former, but we have not looked at the plans. Honestly, until relatively recently enough of this stuff was limited to "what we need and absolutely no more" that it wouldn''t be much help to most people. Apache is about the exception, because it is used enough that it is reasonably flexible.>> * the module enable/disable feature also ships appropriate configuration and >> installs the appropriate packages for the platform. > > Nice, I''d love to add that.We did it the nasty way: define apache::module (...) { case $name { "fastcgi": { package { libapache2-mod-fastcgi: ensure => latest } # ...and if you need config, use apache::conf here. } } } Obviously that is going to be doing more for other platforms than Debian. [...]>> * apache::listen{,::port80,::port443}, which configures the system to listen >> on a custom port, and then wraps that in a class for the standard ports. > > I don''t do it quite the same way, but there is a tunable for the > ports: $apache_listen_ports*nod* We ended up with various services needing to deploy to different ports, and that worked out the best way for them to coordinate that without a single point that set it up.>>> Here''s my proposition, though. Let''s get all the disparate "apache" modules >>> out there merged together into One Awesome Module. What do you think? >> >> Sounds like a great idea to me, but it is a heck of a lot of work. > > Yeah, but I''m going to try anyway.Well, while releasing internal config might be hard, contributing back to an upstream project we use is easy to approve, so I will see how far we would need to change to use your module as the base for what we do. If we can get that I (and my staff) can contribute back enhancements to y''all easily, and I do want to do that — the less code I maintain the cheaper this is for my boss.[1]>> The most likely "next" feature for us, incidentally, will be to try and >> extract the parts of a VirtualHost tag that are custom, and the parts that are >> standard like the header, auth, logging, etc, so that we don''t duplicate those >> in dozens of different files we install... > > I love this idea. Will have to see if I can add something to this module.*nod* My goal was to get the "80 percent" bit right: make it easy to turn on features like injecting a configuration fragment for authentication. My rough thought was to make it dynamic: supply a string name for "auth", and it includes some boilerplate in the right location, and then interpolates a template I supplied with the right name, or something... Not really a finished thought though. Daniel Footnotes: [1] ...and the less it sucks when I got to the next company, since I don''t have to rebuild all that nice infrastructure from scratch. -- ✣ Daniel Pittman ✉ daniel@rimspace.net ☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi> These are the ones I know about: > > 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-apacheor the one at https://labs.riseup.net/code/projects/shared-apache which is developed by several people, works on Centos, Debian and OpenBSD and can even setup itk-specific things and in combination with other modules such as the webhosting [1], you have the possibility to create a whole webhosting account with only a few lines of puppet code. More modules can be found at [2]. cheers pete. [1] https://labs.riseup.net/code/projects/shared-webhosting [2] https://labs.riseup.net/code/projects/sharedpuppetmodules -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkvqXC8ACgkQbwltcAfKi3/f+ACeJ4LDKFGJX2ncOwWIwazMFBPX 7w0AoLRCtyZavAXY4rnGMR+hTJDgzmsQ =k9Ib -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> > 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 > >I''d be delighted to see my apache module be made redundant. Every module I tried either: - had assumptions that I didn''t like (e.g. one depended on augeas and I''m not a fan of machine-edited files), - had baked-in things like file locations from RedHat-style distros (cough *extlookup*) - only worked on Puppet 0.25 for no discernible reason If we agree on some features that we''d all like, then we could describe those in a cucumber spec. And then test it on the matrix of operating systems and Puppet versions - which Hudson ought to do nicely. J. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- "Julian Simpson" <simpsonjulian@gmail.com> wrote:> - only worked on Puppet 0.25 for no discernible reasonI''d consider this a feature at this point. We dont want to be the next php4. -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> > I''ve open-sources Digg''s apache module: > > http://github.com/plathrop/puppet-module-apache > > > > I know this isn''t much more advanced than what I''ve seen a lot of > > people using. Here''s my proposition, though. Let''s get all the > > disparate "apache" modules out there merged together into One > > Awesome Module. What do you think? > > > > One module to rule them all > > One module to find them > > One module to bring them all > > And via Puppet bind them.Excellent initiative ! Things I see missing in most of the apache modules found out there and which we worked on in ours (http://github.com/camptocamp/puppet-apache) include: - abstraction of debian/ubuntu - redhat/centos differences (I agree by debianizing the way apache works on redhat) - management of ssl certificates - selinux support for redhat/centos Furthermore, I''d like to drive your attention to the fact that augeas has experimental support for apache-like configuration files. Maybe would it be an idea to use this to edit config files shipped by the distribution instead of overwriting them with files/templates from the module ? Marc -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> >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-apacheFor 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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On May 12, 2010, at 3:16 AM, Julian Simpson 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 > > > I''d be delighted to see my apache module be made redundant. Every module I tried either: > - had assumptions that I didn''t like (e.g. one depended on augeas and I''m not a fan of machine-edited files), > - had baked-in things like file locations from RedHat-style distros (cough *extlookup*) > - only worked on Puppet 0.25 for no discernible reasonMeaning that it doesn''t work on 0.24.x, or it doesn''t work on rwolf. (The next puppet.)> If we agree on some features that we''d all like, then we could describe those in a cucumber spec. And then test it on the matrix of operating systems and Puppet versions - which Hudson ought to do nicely.-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On 5/12/2010 2:15 AM, Paul Lathrop wrote:> Hey all, > > I''ve open-sources Digg''s apache module: > http://github.com/plathrop/puppet-module-apache > > I know this isn''t much more advanced than what I''ve seen a lot of > people using. Here''s my proposition, though. Let''s get all the > disparate "apache" modules out there merged together into One Awesome > Module. What do you think?Thanks for starting this! Here''s my refined version of one of the "original" implementations: http://github.com/puppet-modules/puppet-apache This modules was started by Tim Stoop "back when". Best Regards, David -- dasz.at OG Tel: +43 (0)664 2602670 Web: http://dasz.at Klosterneuburg UID: ATU64260999 FB-Nr.: FN 309285 g FB-Gericht: LG Korneuburg -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Marc Fournier
2010-May-17 21:37 UTC
[Puppet Users] common module [was: puppet-module-apache]
> 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''ve been thinking about this and about the various attempts to start a "common modules" project that we have seen in the past. I believe the reason it will probably be difficult to build one common apache module that everyone will be happy to use, is that apache is one of these tools that offers many different ways to do the same sort of thing. Then there is the personal/cultural preferences of every sysadmin on how thing should be done. Add this to the various constraints which are imposed to us by the clients/managers which we work for. So either this module will eventually be extremely simple and generic, but will probably not be very useful because all the job of configuring apache will be left to the module user. Or it will be full of cool ideas, will allow the user to skip past the complicated configuration stuff, but will be biased towards the authors habits and constraints. I think this will be the case for any "middleware" tool, not only for apache. By middleware, I mean the tools which the users have direct interaction with (databases, application servers, fileservers, etc). In contrast, ntp, syslog, mta, etc, are much less subject to this problem. Except the sysadmins, nobody usually cares how ntp works, or if it even exists. So what I''m suggesting is that it may be easier to start a set of common modules with this second sort of modules (which probably have at least as many variants as the apache module). Sorry if I sound pessimistic, but to quote Paul, "Let''s get all the disparate apache modules out there merged together into One Awesome Module." seems to me like the 12 labors of Hercules. On the other hand, without ambitious people to start such projects, incredible tools like puppet or apache wouldn''t exist :-) I''m looking forward to debate this around a belgian beer in Ghent ! Marc -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.