Exactly what I'm experiencing as of 12 hours ago. Also on OS X... I compiled ruby-191-p376 from source, updated gems and installed all dependent gems...then built merb gems from git master. Same results as you describe (I'm using thin, not mongrel). I'm not using bundler. Its there, but the app runs on system installed gems. I have a working stack using ruby-191-p243 and a merb 1.1 edge build from a few months back and all works well. Any ideas?? This appears really busted at the moment. thanks, Jon
On Dec 22, 3:46 pm, ddellacosta <[email protected]> wrote: > Hi folks, > > I've been having trouble with this combination. At first I thought it > was the fault of something in my old app and other gems I'm bundling > in (I am using the new Bundler too, btw, v. 0.7.2), but I generated a > new app using merb-gen w/a fresh Gemfile and config and whatnot, > generated a really basic resource, and then tried running merb > and...got problems. The basic symptoms are this. > > When I *didn't* have methopara bundled in the Gemfile (note, I do > *not* have it installed system-wide, just bundled in), merb-action- > args seemed to not exist, and any time I'd hit a controller with > parameters Merb would complain with some about the wrong > arguments...this makes sense I guess. > > Now that I *do* have methopara bundled in, Merb just hangs when I hit > a page...any page. The browser spins its gears, Merb log sits on the > "Params:" line. Interesting huh? > > So, did I miss something in all the group posts/wiki/etc. that has > been flying by in the last few months? Any help greatly > appreciated...thanks! > > Best, > Dave -- 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.
