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. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
