[Rails] Re: Rails on mod_ruby

[Eric Anderson]

David Heinemeier Hansson wrote:
> FastCGI is the preferred production environment for Rails. Unlike 
> mod_ruby, applications won't walk all over each other in the shared 
> interpreter. Due to this walk-over fact, it's not safe to run more than 
> one Rails application per mod_ruby setup.

OK, when I get back to playing with Rails I will just run it as a fcgi. 
Curious though. Shouldn't fcgi have the same problems? After all you 
have only one interpreter running. Of course I guess the difference is 
that you have each rails app (and other apps) running in a different 
instance of the interpreter so another program can get access to the 
rails program. What about updates to rails apps? If I change a rails 
file will I have to restart the apache to get it to restart the fcgi? Or 
can I somehow just kill the fcgi and then apache will relaunch it when 
it realizes it was killed?

It is starting to sound like for development I should just be using the 
CGI interface. On production I can put the app in fcgi or mod_ruby but I 
will have to turn off auto-reload on mod_ruby and restart apache anytime 
I deploy the development code to production. Is this a correct assessment?

Eric
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: OpenPGP digital signature
Url : http://one.textdrive.com/pipermail/rails/attachments/20041209/bee0296d/signature.bin