On Fri, Mar 19, 2010 at 3:33 PM, Brice Figureau <brice-pup...@daysofwonder.com> wrote: > On 19/03/10 20:31, Michael DeHaan wrote: >>> I vote that what we really need is a "Puppetmaster Server Options" >>> page with a brief overview of the different options and the benefits >>> of each. >>> >>> It's really quite complicated at the moment >>> >>> Webrick >>> Apache with Passenger >>> Apache with mod_proxy and mongrel >>> Pound with mongrel >>> Nginx with mongrel >> >> Yeah, if we generalized our mailing list advice now, it (correct me if >> I'm wrong) seems to imply "start out with webrick and learn how it >> works, if you can, upgrade to Passenger, and if you can't, use >> Mongrel?). >> >> (Also ... Are many folks are using Pound and Nginx?) > > I do use nginx (and mongrel). I got some nginx patches accepted upstream > for a complete support of CRL, so it is even easier to now use nginx for > a master. Nginx also allows file content offloading relatively easily > (see my blog for an example, more to come soon on this front).
Where's this entry Brice? >> I like choice, but I think it would be great if we could have a >> favored option, for people who didn't want to do the research. > > I think the current consensus is for Passenger. But I'm wondering if > it's because it's the REE companion or because it's superior to mongrel. For me it's because it is easier to manage and monitor. I'm not even using REE at the moment on Hardy, benchmarking isn't showing enough of an improvement to justify maintaining the packages. > BTW, there is a well maintained Passenger module for nginx. > >> Right now that seems to be Apache+Passenger, but not saying we >> couldn't change that later. > > Correct. > >> (and if perchance jruby is easier to use from distro packages and >> meets requirements, more power to it? or no?) > > I'm able to run puppet on JRuby, but it seems I'm the only one :-) > So, I guess it's not yet ready for showtime. I have made more progress since we last chatted, but got distracted with other things at work. I don't have all functionality, but I have most things working fine, and the bits that are seem *much* faster. > > The stack is relatively easy to come with: > - a reverse proxy (mainly to be an ssl endpoint) > - a servlet container (ie jetty or glassfish (available in a gem) > - a glue to rack (jruby-rack, usually embedded in the previous layer) > - puppet > - jruby > > -- > Brice Figureau > My Blog: http://www.masterzen.fr/ > > -- > 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. > > -- 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-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.
