People using the Rails SCGI runner?

Hi,

I'm currently maintaining the Cherokee package in Debian. I
know many
people want to use Cherokee with Rails applications - and it
only
makes sense to package and make available the Rails SCGI
runner
[1]. I have been working on getting the package ready for
upload in
Debian as well (you can get my preliminary version [2] if
you are so
inclined). 

Now, there is only one point left preventing me from sending
the
initial upload of this package: Every executable in Debian
must have
its manual page, and I came up with what seems like a decent
manpage
for scgi_ctrl (I'm attaching it converted to text to this
mail). However, I'm not yet much of a Rails SCGI Runner
user, so I
fail to understand many of the semantic differences between 
scgi_ctrl and scgi_cluster (although it sounds obvious, but
the
invocations are too similar).

Is anybody among you a Rails SCGI user? Can you help me fill
this
void? 

I'm sending this message to several lists where I think the
right
audience can be found  Of course,
I'm not cross-posting it, but some
of you might get this message more than once.

Greetings,

[1] http://www.zedshaw.com/projects/scgi_rails/index.html

[2] http://people.d
ebian.org/~gwolf/ruby/

-- 
Gunnar Wolf - gwolfgwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973  F800 D80E F35A 8BB5
27AF
scgi_ctrl(1)                                                
     scgi_ctrl(1)



NAME
       scgi_ctrl - Control and configure individual SCGI
processors

SYNOPSIS
       scgi_ctrl [options] COMMAND [options] [COMMAND
[options] ...] [args]

DESCRIPTION
       The  SCGI Rails Runner server is an environment under
which you can run
       your Rails applications, and scgi_ctrl is its main 
controlling  inter‐
       face.

       Please  note that this implementation is still in its
early stages.  It
       works reliably, but the user interface (i.e.
displaying  the  different
       possible  error conditions) is really unpolished. 
For most actions, no
       output means a success state, while any ugly errors
(usually as a stack
       trace dump) mean a failure state.

OPTIONS
       The following global options are defined for
scgi_ctrl:

       -u, --control-url URL
              DRuby URL to run control on (same as SCGI
-1000)

       -c, --config PATH
              Config file to use (#{SCGI:EFAULT_C
ONFIG})

       -h, --help
              Show help

       -v, --version
              Show the version of the program

       scgi_ctrl  can  be  called  with any of the following
commands, some of
       which have their own options:

       config Generate the configuration for the SCGI server
 for  a  specific
              application.   This  command  should  be 
called from within the
              application’s main directory (this means,
the  Rails  root,  not
              the  app/  directory).   As  a  result, 
scgi_ctrl will create a
              scgi.yaml file inside our config/ directory.

              -e, --env STRING
                     Rails environment to use

              -h, --host STRING
                     IP address to bind the SCGI server to

              -p, --port NUMBER
                     Port to bind to (defaults to 9999)

              -l, --log-file PATH
                     Which log file to use. Defaults to
log/scgi.log

              -t, --throttle NUMBER
                     Maximum connections per second to
allow.

              -m, --max-conns NUMBER
                     Max simultaneous connections to  allow 
before  the  busy
                     message gets displayed

              -S, --disable-signals
                     Turn  off  POSIX signals processing,
leaving only network
                     control

              -D, --disable-net
                     Turn off network control processing,
leaving  only  POSIX
                     signals

              -P, --moron-mode PASSWORD
                     You  want  to  specify your password in
the command line.
                     Seriously, this should never be  used 
if  you  care  the
                     least about security.

              -M, --merge
                     Reconfigure  the  SCGI  runner, merging
new settings with
                     previous rather than generating a new
configuration using
                     the default values

       help   Provide  help  for individual commands.  This
command prints the
              program help if no arguments are given.  If
one or more  command
              names are given as arguments, these arguments
are interpreted as
              a hierachy of commands and the help for the
right  most  command
              is show.

       list   List the currently running SCGI processors

       monitor
              Monitor the application.
              This  command  will  connect  to a running
SCGI server, and keep
              updating/displaying the process’
configuration and status  (this
              is,  the  same output that the status command
gives) in the cur‐
              rent console

       reconfig
              Reconfigure the running SCGI servers with new
values in the con‐
              figuration file

       restart
              Restart the SCGI server

              -f, --force
                     Forced shutdown rather than graceful
(default graceful)

       start  Start the application server.
              Keep in mind that the server is started as a
daemon, so you will
              get no output (except in the case the server
is already running,
              which will cause the new invocation to return
an error message)

              -r, --run-path PATH
                     Change to this directory before trying
to start

       status Get the application’s status and basic
configuration data.

       stop   Stop the application

              -f, --force
                     Forced shutdown rather than graceful
(default graceful)

       version
              Show the version of the SCGI runner

SEE ALSO
AUTHOR
       scgi_ctrl  and  the SimpleCGI protocol implementation
for Ruby on Rails
       were written by Zed a. Shaw <zedshawzedshaw.com>

       This manual page was written for  the  Debian  system
 by  Gunnar  Wolf
       <gwolfdebian.org>.  Most  of  the manual page
was taken literally from
       the program code or output, so it might be used and
redistributed under
       the same terms as the program itself.



SCGI Control                      2006-11-09                
     scgi_ctrl(1)
_______________________________________________
Cherokee mailing list
Cherokeecherokee-project.com
http://cherokee-project.com/cgi-bin/mailman/listinf
o/cherokee