When I start up a new Rails 3 project (i.e. one fresh after a
`rails new` command), mongrel appears to start (creates a pid file, and
reports no errors on the CLI), but the app does not load in the browser
and I find this in the mongrel.log
/gems/ruby-1.8.7-p302/gems/activesupport-3.0.0/lib/active_support/dependencies.rb:239:in
`require': no such file to load -- dispatcher (LoadError)
The most relevant info I could find is this, which seems to suggest that
mongrel is stuck in an abandoned, buggy state relative to Rails 3
(unless I misinterpreted the conversation).
http://github.com/fauna/mongrel/issues#issue/2
Is mongrel even being maintained anymore?
--
Posted via http://www.ruby-forum.com/.
Regards,
Fidel.
> --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To unsubscribe from this group, send email to
> rubyonrails-ta...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/rubyonrails-talk?hl=en.
>
>
...but you'd almost always want to use Passenger instead.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
I've had several problems with Passenger in the past, and never been
able to get any answers about them, so it makes me rather hesitant to
try to use it again. Bad taste, first impressions and all that... but I
suppose there's no alternative.
Well, that would be the issue I am seeing then (-d) as my interest in
using mongrel even for dev is eliminating the need for an open console
window. I tend to have several local rails app running, and console
windows all over is a drag.
Passenger has always worked perfectly for me. No hesitation is
necessary. It's the best Rails deployment solution I'm aware of, and
it's very widely used. Clustered Mongrels are torture to set up (yes,
I've done it -- never again without a specific reason).
Perhaps if you were to ask your questions instead of spreading FUD, you
could get help.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
So use a tabbed terminal. Running in daemon mode for dev is a bad idea
IMHO.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
Hongli, I'll try it, but for the record (and for those afraid of
fud-mongering), here's the details of the problems I had...
These are very old now, and probably don't apply to the new versions of
everything involved (Passenger, Ruby, Rails), but they're the problems I
faced, and never did get answers for. I was never able to use Passenger
because of them, and it made me leary of ever using it because I still
use the same application code that Passenger would not work with back
then. I don't expect answers to these now--don't waste your time on
it--I'm just pointing them out.
Here's hoping the third time is the charm...
-- gw
As does Apple's Terminal.app since Leopard.
> On the Windows side I recommend this:
> http://sourceforge.net/projects/console/
Best,
Not exactly. But Mongrel 2 is coming along: http://mongrel2.org/home
Alternatively, if you don't want Passenger running locally or don't like
it try:
Unicorn is pure Ruby and works perfectly with Rails3 -
http://github.com/defunkt/unicorn
Thin is always an option too - http://code.macournoyer.com/thin/
And as of very recently if you want a local Passenger that works much
like Mongrel then:
gem install passenger --pre
cd your_project
passenger start
This will install and setup Phusion Passenger Standalone the first time.
Then just do 'passenger start' in place of 'rails server'.
This is what I'm now using for development and am very happy with it so
far.
Interesting. With Rails 2, I've always thought local Passenger was
silly, but if Mongrel doesn't work with Rails 3, then I'll try this when
I start working with Rails 3.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
Or they were just trying to provide examples for several common choices.
Best,
--
Marnen Laibow-Koser
http://www.marnen.org
mar...@marnen.org
Looks like the Rails team thinks you should want to use Unicorn, asits gem is included (commented out, but there) in the default Gemfilethat gets generated with any new Rails3 app...
Or they were just trying to provide examples for several common choices.
Best regards
Peter De Berdt
Thanks everyone for the feedback on the mongrel alternatives.
-- gw