Yep Matt, that's the biggest problem I see with the Mongrel. The development will stop rather sooner than later especially with alternatives which are alive such as Unicorn or Passenger or Thin & friends.
Pavel On Nov 8, 7:39 pm, Matt Aimonetti <[email protected]> wrote: > For the record, I have a mongrel fork that's 1.9 compatible and patches were > provided to Evan, however it looks like Twitter might switch to passenger > and I don't know if they will maintain mongrel much longer. > > - Matt > > > > On Sat, Nov 7, 2009 at 2:22 PM, botanicus <[email protected]> wrote: > > > Have you bother to read what Pavel wrote about the Ruby 1.9 support? I > > think this is pretty reasonable argument. > > > On Nov 7, 1:44 pm, Matthew Beale <[email protected]> wrote: > > > Yeah please. Changing the server setup right in the middle of 1.0's > > > releease was a complete mess. Let's not do that again :-) > > > > -- > > > Matthew Beale :: 607 227 0871 > > > Resume & Portfolio @http://madhatted.com > > > > On Fri, 2009-11-06 at 10:48 -0800, Matt Aimonetti wrote: > > > > Whatever, changing such a critical aspect of Merb right before a major > > > > release doesn't seem wise at all. > > > > My suggestion: release 1.1, and play with unicorn in a separate > > > > branch/trunk. Once it's ready and you know it's reliable and better > > > > than the existing solution, then push a new release. > > > > > - Matt > > > > > On Fri, Nov 6, 2009 at 10:40 AM, Ezra Zygmuntowicz > > > > <[email protected]> wrote: > > > > > Unicorn is by far less buggy then the current > > > > forking/master/worker > > > > stuff in merb. I say go for unicorn support. > > > > > -Ezra > > > > > On Nov 6, 2009, at 10:32 AM, Yehuda Katz wrote: > > > > > > I agree > > > > > > On Fri, Nov 6, 2009 at 10:22 AM, Matt Aimonetti > > > > <[email protected] > > > > > > wrote: > > > > > I think that making unicorn the default adapter is not a > > > > very good > > > > > idea. > > > > > It still has lots of bugs and should be handled with > > > > caution. > > > > > > I also think that it might not be worth delaying 1.1 to add > > > > unicorn > > > > > support. > > > > > > - Matt > > > > > > On Fri, Nov 6, 2009 at 3:56 AM, Pavel Kunc > > > > <[email protected]> > > > > > wrote: > > > > > > Unicorn support could come earlier than 1.2. I'd like to > > > > bundle it > > > > > with the 1.1 if possible because it would allow out of box > > > > 1.9.1 > > > > > experience. I'd also made unicorn as default adapter. So I > > > > think we > > > > > can try for now to write unicorn adapter and just plug > > > > unicorn to merb > > > > > the same way as other servers. > > > > > > We can than decide what to do with the bootstraping. > > > > > > Pavel > > > > > > On Nov 6, 3:17 am, Yehuda Katz <[email protected]> wrote: > > > > > > I would be in favor of removing the Merb bootstrap stuff > > > > in favor of > > > > > > unicorn, which is basically the same code but made more > > > > generic. > > > > > > > We could do that for 1.2 for sure. > > > > > > > -- Yehuda > > > > > > > On Thu, Nov 5, 2009 at 6:29 PM, Nicholas Orr > > > > > <[email protected]> wrote: > > > > > > > > I had a go at running merb via unicorn and had the same > > > > > experience. > > > > > > > > My guess was that because merb does it's own bootstrap > > > > stuff then > > > > > > > launches (forks?) thin/mongrel - this is where running > > > > with > > > > > unicorn > > > > > > > falls over. > > > > > > > > As you can see in the unicorn_rails start script it is > > > > very > > > > > different > > > > > > > from the unicorn script and basically satisfies rails > > > > way of doing > > > > > > > things. > > > > > > > > One thing I didn't try was starting with a working > > > > passenger > > > > > config.ru > > > > > > > - that may have resulted in a working solution... > > > > > > > > A goal of 1.2 might be have merb behave more rack like > > > > so one > > > > > could > > > > > > > use rackup - then merb could slot into everything > > > > (middlewares, > > > > > rack > > > > > > > stack) else rather than the current situation that > > > > everything > > > > > can slot > > > > > > > into merb... > > > > > > > > Nick > > > > > > > > On Fri, Nov 6, 2009 at 12:51 PM, scottmotte > > > > > <[email protected]> wrote: > > > > > > > > > Hi guys, > > > > > > > > > Any thoughts on why using unicorn to run merb would > > > > quickly > > > > > load up > > > > > > > > the merb app, close it down, then respawn and try > > > > again - and > > > > > then > > > > > > > > repeat that over and over again. > > > > > > > > > The config.ru file is the same I'd use for thin, and > > > > I'm on > > > > > the latest > > > > > > > > Merb 1.1 from wycats github. > > > > > > > > > #my config.ru > > > > > > > > require 'merb-core' > > > > > > > > Merb::Config.setup(:merb_root => ".", :environment => > > > > > ENV['RACK_ENV']) > > > > > > > > Merb.environment = Merb::Config[:environment] > > > > > > > > Merb.root = Merb::Config[:merb_root] > > > > > > > > Merb::BootLoader.run > > > > > > > > > use Merb::Rack::Static, Merb.dir_for(:public) > > > > > > > > run Merb::Rack::Application.new > > > > > > > > > # if you want to try unicorn yourself. > > > > > > > > The command to setup and run unicorn is: > > > > > > > > sudo gem install unicorn > > > > > > > > cd yourapp > > > > > > > > unicorn # alternatively to try on a rails app it's > > > > > 'unicorn_rails' > > > > > > > > > I'm asking this in the unicorn forum too. > > > > > > > -- > > > > > > Yehuda Katz > > > > > > Developer | Engine Yard > > > > > > (ph) 718.877.1325 > > > > > > -- > > > > > Yehuda Katz > > > > > Developer | Engine Yard > > > > > (ph) 718.877.1325 > > > > > Ezra Zygmuntowicz > > > > [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en -~----------~----~----~----~------~----~------~--~---
