bradley taylor wrote:
> Hey y'all:
> mongrel_cluster provides management tools for running Mongrel behind
> a reverse-proxy/load balancer. It is an extraction from Rails
> Machine, a deployment service and Ruby library that simplifies Rails
> application deployment. This release fixes bugs and adds a Capistrano
> task library.
>
> Good luck and let me know how it works for ya!
This has been VERY helpful, thanks! Two things have come to mind that
might be helpful to include in a future release:
1. Parse the mongrel_cluster.yml file through ERB, like Rails does for
the fixtures and database.yml file. Would allow for things like setting
the CWD to ENV['HOME'], etc. Rails uses:
YAML::load(ERB.new(IO.read(database_configuration_file)).result)
2. Provide a cluster command for starting up "missing" Mongrel servers.
The issue is that "restart" only restarts processes that are actually
running. And just running "start" will do _bad_ things if you just run
it; it appears to put a new pid into the .pid file, but then fail to
start up (since a process is running already on that port) -- the net
effect is that the process is now orphaned, since you don't know the pid
anymore.
I guess I'm looking for something like the fcgi spinner, that can start
up Mongrel processes if they die. And allow restarts to turn into a
plain old start, if the target process isn't found.
_______________________________________________
Mongrel-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/mongrel-users
