similar to: Mongrel 0.3 -- Runs Ruby On Rails

Hello Everyone, Today''s Mongrel is the first release to sport spiffy pre-built win32 gems. This comes thanks to Wilson Bilkovich donating some Rakefile magic that does the stuff for me. Everyone who uses win32 should send Wilson a thank-you since without him you''d be a victim of my laziness for at least a few more weeks. People who are testing and trying Mongrel out should

I don''t think there''s a way to do that other than using a proxy (ISAPI_REWRITE) or just a server-side redirect. I''d love to be proven wrong though. -----Original Message----- From: rails-bounces@lists.rubyonrails.org [mailto:rails-bounces@lists.rubyonrails.org] On Behalf Of frazer horn Sent: Wednesday, March 15, 2006 9:13 AM To: rails@lists.rubyonrails.org Subject:

Hey Folks, This is a quick release that fixes a major bug. I forgot to require the timeout library properly in mongrel.rb so people using Mongrel outside of Rails would see pauses. 0.3.3 fixes this all up. The 0.3.3 release also has a small change to the examples/simpletest.rb file with some gzip response using Ruby''s zlib support. Curious what people think about this and whether it

160,000 pages 99% static, only minor stuff done in rail (search, contact us, etc.) windows server 2003 Ror 1.0 Currently 30K Hits /day on IIS. Apache or Lighttp? Fast_CGI seems kinda slow with a 2003/Apache configuration. The only thing I''ll get rid of for sure is IIS. -Cedric -- Posted via http://www.ruby-forum.com/.

I did some basic speed test on my rails application. I use Centrino 1.7GHz, WinXP. For simple test I used Apache ''ab -n 100 -c 10 http://url.... '' Running Mongrel 0.3.11 I got: development env. = 4.5 req./sec production env. = 11.5 req./sec Running Webrick I got: development env. = 5.7 req./sec production env. =25.9 req./sec Does anyone know why the webrick is still faster?

Hi, After following advice from you good folks, I gave mongrel a try in a cluster design based on the example on the Mongrel website - and it worked right out of the box which is great - and it''s very fast :) I have got a bit stuck though. I have two MS Word files in /public/files/. I can pull back these files no problem but it isn''t sending a mimetype. I think I have two

Hello All, Yet another release of Mongrel proudly pushed out for everyone to review and comment on. This time though, I''ve done up a little website that''s *way* better than the plan Rdoc that used to stand in for the site like a one-legged leper. * http://mongrel.rubyforge.net/ As you should already know, Mongrel is a fast HTTP server and library for Ruby partially written in

I tried using the killall -USR1 mongrel_rails to check on a problem, and all I get is mongrel_rails: no process killed Nothing shows in the log. Any ideas? I''m using the latest pre-release, and a ''ps'' shows my cluster is running. Cheers, Brett

Hello Everyone, This is the official 0.3.13.3 release of Mongrel. Mongrel is now released under the *Ruby license* instead of the LGPL. I''m hoping this increases the adoption of Mongrel even further and hopefully I can start pushing to get Mongrel included in Ruby directly. INSTALL As usual, you install it with your friendly gem install method of choice: gem install mongrel Or

Hi all, as part of adopting Rails in my company I had to go through the hassle of setting up a Rails production environment on Win32 system since we mostly use MS SQL as our database back end and also because we mostly dealing with customers who become green-blue-purple as soon as you mention Unix/Linux and run for the door. I also need to mention that most of our web applications are internal and

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 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

Hey Folks, I''ve been holding off the official 0.3.13 release so that Luis can get the win32 side very nice and clean. We fixed a major problem last night so it''s only a short time before we get it out. Luis is working really hard on it, so just be patient. In the meantime, I''ve been doing a code audit of the Mongrel code as it is now and fixing any little things I

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

I do some indexing using acts_as_ferret in a rails app. I need to do some preloading of the index''s sort fields so that the first request that sorts doesn''t take 5 minutes to complete. I tried sticking my preload code in config/environment.rb and that worked but it gets ran in rake migrations, tests, etc, when it''s not really needed. Is there anything specific to

Following errors are taken from monrgrel running in development mode. It complained routes.rb, no such file or directory and then sometimes i get application.rb, no such file or directory.Doesn''t seem correct to me. Though not so often, but even production servers throw these errors sometimes, and i have no special routes setup or something.Its pretty much default one, except few changes

Following is the output of top command at my server and i find the high usage very much alarming. We are basically a team of three developers working on same machine(remotely), so we run mongrel_rails servers from out ~/public/app directories. We also run a cluster of mongrel servers using apache2.2. Is this much memory use normal? PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+

Hi, I just gave Mongrel a try on my Rails app. After running ''mongrel_rails start'' everything seems fine. Yet, when I start a request I get the following error message on the console: ERROR: You have a nil object when you didn''t expect it! The error occured while evaluating nil.readpartial That''s it. The application works fine with Webrick and

Hello Windows Users! I have finally got my new computer with it''s win32 build working and have just done the first pre-release for 0.3.13 that has win32 support. *** All win32 users should try to grab the pre-release and tell me if it works. *** You can install it with: $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/ >From EITHER win32 or any other platform

I''m using the latest Mongrel (0.3.13.4) and restarting causes Mongrel to die. From mongrel.log: ** USR2 signal received. ** Restarting with arguments: ruby /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails start -C config/mongrel.yml /opt/local/lib/ruby/gems/1.8/gems/mongrel-0.3.13.4/bin/mongrel_rails:142:in `exec'': Operation not supported - ruby

Hey folks, I ran into a few people at RubyConf who were having 99% CPU issues. Please contact me if you meet the following criteria: 1. You are running a production site. 2. You are experiencing 99% CPU errors. 3. This is frequent enough that you cannot manage it. Thank you. Please contact me off-list about it. -- Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu http://www.zedshaw.com/