ruby q
Out of context: Reply #7
- Started
- Last post
- 8 Responses
- myobie0
short answer:
if you go with a host that has rails and fastcgi, you just upload and it works (although some processes get stuck sometimes)
if they use mongrel, you gotta stop and start your app each time you update it...
the long answer:
rails is just a collection of ruby files to help you get started
there is no direct hook into apache for a site written in ruby (except fastcgi)
a site written in ruby runs in memory, so it has to be started like a regular app and it runs in the background listening for requests
you need mongrel and apache 2.2 to do it correctly
you start multiple versions of your app, each with it's own mongrel, then you tell apache to use all of them for the requests (but balance the connections)...
don't use a windows server for rails, you will hate it
it's not like php where you just upload and it refreshes
you gotta stop the app from running in the background and then start it back up...
(unless you are using fastcgi, which will cause you problems because the processes will get stuck and never die)