On Feb 20, 2008 2:33 AM, Jaan J. [email protected]
wrote:
Hi Anibal and glennswest,
Thanks a lot for your help.
I tried to use Mongrel and integrate it with IIS and now it’s working
Thanks guys
Just one more thing, now it’s running for single Mongrel
what i’m trying to do now for next step is I want to run another Rails
application but I dont want to create another Mongrel service
Is not possible use the same ruby process for two different rails
applications.
That is design limitation of Rails and not Mongrel.
I read from somewhere that I can use Mongrel cluster
But after I created mongrel cluster with mongrel_cluster.yml, when I
tried to start my mongrel_cluster service, it returns error something
like this :
Mongrel cluster leverage in functionality only available in posix
compliant OS (forking also known as daemonize). That is not possible
to implement in Windows without replacing things and adding big
conditional blocks to call Win32 API.
In any case, having one service for each application is a good
practice. You can restart each application individually from each
other.
In case you want to implement a “cluster” of the same application,
that’s another story that currently is not doable with
mongrel_service.
Right now the only workaround is creating a service for each application
port:
my-app-3000
my-app-3001
my-app-3002
etc.
Then you can trick all these services to depend on the previous one,
so doing a “net start my-app-3004” will cascade the net start command
down to my-app-3000.
That’s a nice trick but can be tricky get it set (maybe it deserves a
separate post)
Regards,
Luis L.
Multimedia systems
A common mistake that people make when trying to design
something completely foolproof is to underestimate
the ingenuity of complete fools.
Douglas Adams