Me thinks the docs might need a bit of fleshing out 
http://mongrel.rubyforge.org/docs/mongrel_cluster.html
At the very least, what vars can go in its config.
Joe
Right now you find some references to docs about mongrel_cluster at
(scroll
down to boottom):
Joe wrote:
Me thinks the docs might need a bit of fleshing out
same. ive been looking for info on how to serve public/ with mongrelā¦
so far, ive tried various things, including -r public, -r
/absolute/path/to/pubic, about to try making up a mongrel.conf and
setting a DirHandler for ā.ā (hopefully this doesnt interfere with the
existing controller stuff).
i thought maybe it was just choking on symlinks, since dirs in /var/www
are actually linked to /usr/local/src, or maybe a permissions thing, but
seeing as other daemons can read the public files even running as
ānobodyā instead of root, thatās proably not itā¦
On Mon, 2006-05-22 at 22:36 +0200, Joe wrote:
Me thinks the docs might need a bit of fleshing out
http://mongrel.rubyforge.org/docs/mongrel_cluster.html
At the very least, what vars can go in its config.
Yeah, Iām writing those as fast as I can. All this week Iām pretty much
unemploying myself so people can have a release, so stay tuned and
theyāll come soon.
ā
Zed A. Shaw
Hi Joe:
On May 22, 2006, at 4:36 PM, Joe wrote:
Me thinks the docs might need a bit of fleshing out
http://mongrel.rubyforge.org/docs/mongrel_cluster.html
At the very least, what vars can go in its config.
You donāt need to mess with editing the config file at all. Just use
the ācluster::configureā command and it will write the file for you.
The command takes the same arguments as the āstartā command and
respects its default values. You can see all the options by doing
āmongrel_rails cluster::configure -hā.
Example, 8 mongrels in production environment starting at port 8000
bound to localhost for use behind a balancer.
Configure:
mongrel_rails cluster::configure -p 8000 -e production -a 127.0.0.1 -N 8
Start:
mongrel_rails cluster::start
Stop:
mongrel_rails cluster::stop
If you donāt call these from RAILS_ROOT, then use āāchdirā to set
RAILS_ROOT when configuring. You can also write the configuration
file to a specfic directory using āāconfigā. To start/stop use āā
configā to tell the command where to read the configuration from.
Good luck,
Bradley Taylor
Rails Machine
Simplified Ruby on Rails application deployment
http://railsmachine.com
just use mongrel it as you would use webrick. it just works. no
configuration needed. If you have a special setup, take a look at the
help
options, if you move to production, just add mongrel-cluster, it also
just
works, and again the help options will inform you how, there is no
special
thing about symlinks and that stuff you mentioned ā¦