I’ve understood that the mod_ruby apache module is not recommended for
running Ruby on Rails applications. But I haven’t found any information
as to why that is so. Please enlighten me. And could you point me to the
(currently) prefered production environment. (That can handle both RoR
and PHP sites).
On Apr 27, 2006, at 6:27 AM, Hans-Eric Grönlund wrote:
Thank you and best regards
Hans-Eric Grönlund
–
With mod_ruby you can only run one rails app in one apache install.
Because mod_ruby embeds a ruby interpreter inside of the apache
process. So more then one rails app and they would step on each
other. But mod_ruby is not that bad for web sites built with ruby but
not rails. I have a few sites where I can use .rhtml and .rb files
and they are executed by apache as ruby files. FOr sopme dead simple
sites this is a nice lighweight way to go. But for rails apps
mod_ruby leaves a lot to be desired.
Hi! I’ve understood that the mod_ruby apache module is not
recommended for running Ruby on Rails applications. But I haven’t
found any information as to why that is so. Please enlighten me.
And could you point me to the (currently) prefered production
environment. (That can handle both RoR and PHP sites).
The reason mod_ruby isn’t recommended is that it is very, very,
very, very slow. Simple as that.
No, it isn’t. Maybe when Rails runs atop it, but not in general.