Ah. As Vivek mentioned above, I'm trying to start merb from within the
GlassFish application server, so while it's a regular application
layout, it's not a normal boot process. The process that I'm using to
start merb up seems to also break static file handling, so I'm trying
to get that to work again. Right now, I've got the following to
initialize it:
Merb::Config.setup(:merb_root => "#{$glassfish_appRoot}")
Merb::Rack::Adapter.register %w{grizzly}, :GrizzlyMerb
Merb.config.adapter = 'grizzly'
Merb.config.log_stream = JRuby::Rack::GrizzlyLog.new
Merb.disable(:signals)
Merb::BootLoader.run
After which I call Merb::Rack::Application.new whenever I need a new
merb instance. That brings merb up, and allows it to serve pages, but
it doesn't seem to be recognizing static pages as static (looking
instead for eg. a "stylesheets" controller), so I'm trying to figure
out how to re-connect that properly.
On Oct 23, 12:26 pm, "Michael Klishin" <[EMAIL PROTECTED]>
wrote:
> 2008/10/23 [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>
>
>
> > We need Merb to be handling the static resources rather than the web
> > server. When I use
> > Merb::Config.setup(:merb_root => "#{$appRoot}/public"), Merb doesn't
> > compile any routes, and when I use
> > Merb::Config.setup(:merb_root => "#{$appRoot}"), Merb doesn't find
> > static content.
>
> If you use regular application layout you should not bother setting
> Merb.root manually.
> Check you rackup file (config/rack.rb) or remove it to use default one
> that assumes static assets are
> served from public.
> --
> MK
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
