I would like to unify the ferret_start and ferret_stop scripts into a
single script.  My motivation is to make the scripts more like the other
rails scripts, and to also make it fit into monitoring schemes better.
I realize that some work was done recently to allow the scripts to be
run from script/runner, but I think a unified script is a better
approach.

A unified script would allow more advanced command line processing
without duplication.  For example, being able to supply the RAILS_ENV on
the command line, and overriding configuration options such as the PID
file.

Would there be any objection to me submitting patches that unified these
two scripts?  Here is what I would expect them to look like in the
future (after my patches):

script/ferretd -e production start
script/ferretd -e production stop
-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk

Reply via email to