2009/4/19 Christian Hofstaedtler <[email protected]>: > > Integrating rack nicely has multiple aspects, and I seek input on > all of them: > > * Passenger (AKA mod_rails for Apache) shall again be supported > (see wiki:UsingPassenger). Passenger obviously expects rack applications > to completely follow the rack specification, including the need for > a "config.ru" file which contains the application startup code. > > For 0.24.6 we had an ext/passenger/config.ru, which mostly consisted > of copy-pasted code from bin/puppetmasterd. This is clearly not > ideal, as it has to be maintained seperately and can't be tested > easily. > > Also, some Puppet code assumes, that the puppetmaster process is > named puppetmasterd. This is problematic ($0 will usually be "Rack" > or something). > > Right now, I've Passenger working, with a 3-line config.ru + > http://github.com/zeha/puppet-rack/blob/340d21f80b4cc0b786b259ccac091adce02f3fb6/lib/puppet/network/http/rack_server.rb > > I can't think of a good place where to put this code; or how this > and lib/puppet/application/puppetmasterd could be unified, without > causing too much complexity.
I've got some work part way through doing this, I'll pull your patch and look at the tests. Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
