Hi Charles,
Charles Oliver Nutter wrote:
> On the #jruby IRC channel today we were discussing what our ideal Rails
> deployment setup of the future might be. The two existing options being
> actively explored are:
>
> - deploying JRuby with Mongrel behind some load-balancing software
> (familiar to Rubyists)
> - deploying JRuby as a WAR file within an app server like GlassFish
> (familiar to Javaists)
>
> But the discussion eventually turned toward Grizzly. Almost everyone
> agreed that a "bare" Grizzly instance fronting N JRuby instances running
> Rails would be perhaps the best balance of both worlds. But they also
> all agreed that it would be necessary to have a "gem" of Grizzly users
> could install, allowing them to get going as easily as with Mongrel.
>
> gem install grizzly-rails
> cd myapp
> jruby script/server grizzly
> ...and a scalable server starts up
>
> I'm not sure when one of us will have a chance to work on this, but if
> anyone on the list is interested in such things you can feel free to get
> it going. Obviously there's already Rails support in Grizzly, but it
> needs to be updated to current JRuby and made cleaner/more configurable.
> But I think there's a lot of potential here if we can make a one-shot
> installable Grizzly-based server for JRuby on Rails.
I would be interested to work on it, but I need guidance on where to
start (specifically how to create a gem, where to upload it, etc.). One
thing that we need to do is to port the Grizzly 1.0 implementation to
1.5. This shouldn't be difficult as the API used are mostly the same.
maybe we can discuss this during the conference call today (let's say
the first 15 minutes)?
Thanks
-- Jeanfrancois
>
> - Charlie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>