# \[ANN\] New Mongrel 0.3.13 Documentation: HOWTO Do Everything **URL:** \ **Category:** Rails\ **Created:** [May 13, 2006, 1:08am UTC](https://www.ruby-forum.com/t/ann-new-mongrel-0-3-13-documentation-howto-do-everything/60392 "2006-05-13T01:08:04Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Zed\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/da6949/32.png) [@Zed\_S](https://www.ruby-forum.com/u/Zed_S)\ **Post date:** [May 13, 2006, 1:08am UTC](https://www.ruby-forum.com/t/ann-new-mongrel-0-3-13-documentation-howto-do-everything/60392/1 "2006-05-13T01:08:04Z")
Just a quick note for a few new features/fixes available on the Mongrel pre-release and a new document that covers nearly all the big features and configurations for Mongrel. First, the document is [http://mongrel.rubyforge.org/docs/howto.html](http://mongrel.rubyforge.org/docs/howto.html) and it covers: - All the start command options including the fresh -G option to generate a config for -C. - The format and usage of the MIME type file (-m option). - Using a YAML config file to set command line options (-C option). - Writing fancy Mongrel co - Improved “HOWTO”:/docs/howto.html documentation with all options.nfig scripts in Ruby (-S option). - The POSIX signals Mongrel uses for restart, stop, and reload. - What the super debugging -B option produces and when to use it. - Quick start on installing the mongrel\_cluster GemPlugin. The current pre-release now has the following fixes: - A fix for --num-procs and --timeout where they weren’t really being set. - A new -G option for generating YAML configs for the -C option. Everyone should update from the releases directory with: $ gem uninstall mongrel $ gem install mongrel --source=[http://mongrel.rubyforge.org/releases/](http://mongrel.rubyforge.org/releases/) And try these out. Especially the --num-procs and --timeout since they weren’t really being set previously (damn that’s dumb). Luis is also asking to hold off on the official 0.3.13 release until he can fix up the win32 side and clean up the commands used there. He’s got goodies in the works so that win32 folks can use the same mongrel\_rails script everyone else is using, but get special win:: commands for managing the services. Enjoy! – Zed A. Shaw > **[Zed A. shaw](https://zedshaw.com/)** > > Personal essays and writings by Zed A. Shaw. [http://mongrel.rubyforge.org/](http://mongrel.rubyforge.org/) ---
**Author:** ![Zed\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/da6949/32.png) [@Zed\_S](https://www.ruby-forum.com/u/Zed_S)\ **Post date:** [May 13, 2006, 1:51am UTC](https://www.ruby-forum.com/t/ann-new-mongrel-0-3-13-documentation-howto-do-everything/60392/2 "2006-05-13T01:51:07Z")
On 5/12/06, Zed S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Just a quick note for a few new features/fixes available on the Mongrel > pre-release and a new document that covers nearly all the big features > and configurations for Mongrel. Either something messed up when I installed or something else is just broken. In trying some commands I’m getting errors: mongrel\_rails --version INVALID COMMAND: Plugin /–version does not exist in category /commands Available commands are: - restart - start - stop Each command takes -h as an option to get help. mongrel\_rails start --version INVALID COMMAND: uninitialized constant Mongrel::Command::Base::MONGREL\_VERSION Available commands are: - restart - start - stop Each command takes -h as an option to get help. (Was getting errors trying to use the -G option, but that turned out to be my own fault) jt ---
**Author:** ![Zed\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/da6949/32.png) [@Zed\_S](https://www.ruby-forum.com/u/Zed_S)\ **Post date:** [May 13, 2006, 4:22am UTC](https://www.ruby-forum.com/t/ann-new-mongrel-0-3-13-documentation-howto-do-everything/60392/3 "2006-05-13T04:22:32Z")
On Fri, 2006-05-12 at 19:47 -0400, John T. wrote: > Either something messed up when I installed or something else is just > broken. In trying some commands I’m getting errors: > > mongrel\_rails --version > INVALID COMMAND: Plugin /–version does not exist in category /commands > Available commands are: This is sort of right, mongrel\_rails itself doesn’t have any options, it’s just a script that runs other commands. I should probably just make a version command though. > INVALID COMMAND: uninitialized constant Mongrel::Command::Base::MONGREL\_VERSION > Available commands are: Damn, bug. I’ll fix that up and re-release. Thanks for testing. Let me know how it works otherwise though. – Zed A. Shaw > **[Zed A. shaw](https://zedshaw.com/)** > > Personal essays and writings by Zed A. Shaw. [http://mongrel.rubyforge.org/](http://mongrel.rubyforge.org/) ---
**Author:** ![Zed\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/da6949/32.png) [@Zed\_S](https://www.ruby-forum.com/u/Zed_S)\ **Post date:** [May 13, 2006, 10:23am UTC](https://www.ruby-forum.com/t/ann-new-mongrel-0-3-13-documentation-howto-do-everything/60392/4 "2006-05-13T10:23:09Z")
On Fri, 2006-05-12 at 22:29 -0400, John T. wrote: > ``` > -e, --environment ENV Rails environment to run as > -d, --daemonize Whether to run in the background or not > > ``` > > … > -h, --help Show this message > –version Show version > > Says there already is one 🙂 Ooooh, a smartass. I love it. 🙂 Well, I don’t want to shoot you down for your enthusiasm, but if you read the above you got help for the start command, and it says there’s a –version for that (not for all of mongrel\_rails). Sure, it’s missing the “mongrel\_rails _start_ [options]” part but I’m hoping that won’t prevent the carefully crafted protocol handler or the ternary search trie URI lookup from functioning correctly. I’ll see if I can squeeze the one word change to the usage line into the latest patch for conditional responses from Dan K. tomorrow. It could be a tough one, but I think it might just make it. While I’m doing that, do you think you could maybe test something other than the version string? I don’t know, maybe a Rails application, or something in Camping, or maybe a nice Nitro app or two. Maybe go grab a protocol fuzzer and try to break the parser? You could try writing a handler or a command as a GemPlugin. Maybe some feedback on the actual options. Hehe, anyway, thanks for reporting this. Just giving you a hard time back. – Zed A. Shaw > **[Zed A. shaw](https://zedshaw.com/)** > > Personal essays and writings by Zed A. Shaw. [http://mongrel.rubyforge.org/](http://mongrel.rubyforge.org/) ---
**Author:** ![Zed\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/z/da6949/32.png) [@Zed\_S](https://www.ruby-forum.com/u/Zed_S)\ **Post date:** [May 13, 2006, 4:31am UTC](https://www.ruby-forum.com/t/ann-new-mongrel-0-3-13-documentation-howto-do-everything/60392/5 "2006-05-13T04:31:53Z")
On 5/12/06, Zed S. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > This is sort of right, mongrel\_rails itself doesn’t have any options, > it’s just a script that runs other commands. I should probably just make > a version command though. 'Cept if you do: mongrel\_rails start -h Usage: mongrel\_rails [options] ``` -e, --environment ENV Rails environment to run as -d, --daemonize Whether to run in the background or ``` not … -h, --help Show this message –version Show version Says there already is one 🙂 jt