similar to: Sites that use Mongrel

I''m spending today writing documentation. I''ll be updating quite a few documents, doing some edits, and adding some user contributed docs. If anyone has documentation suggestions, FAQ questions they''d like included, or things they think are old and stale, then let me know. Swing by the Lingr room: http://www.lingr.com/room/3yXhqKbfPy8 And drop me a line if you want

Hi all... Hopefully this is the last prelease. If people on non-linux systems could post back any problems with cluster::status, I''d appreciate it. Install with: gem install mongrel_cluster --source http://mongrel.rubyforge.org/releases/ Note: This is only an update to mongrel_cluster and not Mongrel or other gems. Details about what''s new (if you missed the first

G''day I''m just wondering if anybody knows of a way to get mongrel_upload_progress working with nginx? I''ve had a fair bit of a look around but havn''t been able to come up with anything, yet. -- - James -------------- next part -------------- An HTML attachment was scrubbed... URL:

Alright folks, after nearly a month of pounding and beating up the Mongrel 1.0 RC1 release we''re putting out the official 1.0.1 release. Read all about it at the (much funnier) news posting: http://mongrel.rubyforge.org/news.html For those people in a hurry, the gems should hit the mirrors and you can install using your usual commands. Refer the the above page for more help.

I heard about a new mongrel plugin or version that''s single threaded and uses non-blocking IO with events. It''s called something like "swifty fly". Anyone have a link for it? Thanks.

Guys, Just for fun, I tried to see (I know, a silly way to test it) how much overhead we have calling the C functions of the extensions. the benchmark script and the results: http://pastie.caboo.se/128646 The naive C extension: http://pastie.caboo.se/128647 I compared 1.8.6 (VC6 and mingw builds) against a fresh checkout of ruby trunk. What I understand from that is 1.9 is slower than 1.8

Hi, I''ve got to active project both running on the last Apache 2.2 and on Mongrel 0.3.13.3. One is running perfectly, the other gets (always on the same pages, but not after each request, it seems to be random) a ProxyError every now and then which leads to the mongrel process being called to die and subsequently slowing down the whole web site. I have to restart the mongrel

Okay, I got off my duff this week and have been finishing Mongrel support for IOWA. I now have two handlers that I need to test. One is similar to the Rails handler, passing request handling to IOWA threads in the same process, and the other allows one or more Mongrel processes to pass requests to one or more separate IOWA processes, with session affinity. Is there any set of standard sorts of

Hello Everyone, I''d like to just officially announce that the new volunteers are in charge and given control of the project. I won''t be doing anything more than helping them get ramped up, but they''ll be in charge of doing all the stuff you folks want and are basically the owners from now on. Everyone in the new volunteer list will probably do a little announce, but

How do I setup a sweeper to restart stale or hung mongrel servers? -- Jared Brown jaredbrown at gmail.com (765) 409-0875 7001 Central Ave Indianapolis, IN 46220 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060907/0994017f/attachment.html

I am going to bet this is a mongrel issue,because this doesn''t happen under webrick. Anyway, I was able to get fckeditor: http://www.fckeditor.net/ to work under rails: http://www.joshuamcharles.com/xhtml/fckrails.php i even saw the part about adding "1. Adding a YAML configuration file. For example, create $(RAILS_ROOT)/config/mongrel_mime.yml with the contents: xml:

Hi, It would be nice if Mongrel would do multiapps in one Mongrel instance. For the moment, I have one Mongrel for each app of my server, each on a different port. For example: http://server:8080/app1 http://server:8080/app2 instead of: http://server:8080/ http://server:8081/ Is that planned? Thanks. -jec -- JeSC - Software et Consulting Jean-Eric Cuendet Ing?nieur HES en

I would like first to introduce my self to the community. I am Steve Beyer and I am interested in learning Ruby, ROR, and how to set up a production server. I am going to use OSX for my client/developement system but I would like to get some advice on what operating system you would recommend for a production server. I want to use Mongrel to start and then move up the ladder as my

Hi One of the two mongrel processes has died in the middle of the night four times in the past 9 days, and I need help debugging this. Each time the symptoms are the same: * Each time I can restart the process via cap -a restart_app. * Before the restart, there is nothing unusual in production.log or mongrel.log. * During the restart, about 100 repetitions of an error message are generated in

Hello, I have been looking at the Ruby/EventMachine. First let me say it look very good. Reactor model with no threads makes for fast reliable server, and I have read about marvelous Twisted framework for Python and am glad to see something similar for Ruby. I am writing network app with Ruby threads now and it very slow, and I try new Ruby 1.9 with native threads that make it much slower.

Morning Folks, As most of you know there were a few people who had the following three bugs: * CLOSE_WAIT: Lots of sockets in CLOSE_WAIT state. * 99% CPU: Mongrel''s getting "stuck" pegged at 99% CPU. * LEAK: Memory leak. I''ve successfully fixed these bugs or attributed them to one main cause: pstore. First, the memory leak was because of a bug in how the GC in Ruby

Just thought I''d let you know that your http parser worked great for creating an http protocol handler for Eventmachine. It wouldn''t take that much effort to use Eventmachine for Mongrel, might be worth a shot just to see how it does. A few things would need to be restructered, like HttpRequest where you read the rest of the body, and calling the handler. But it

Hey folks, I''m working on the Mongrel book with Zed, and wanted to get some feedback from the core users (this list) about how they use Mongrel. That sounds a bit vague, but I''m interested in hearing things about frustrating problems / workaround, preferred configurations, if you have a particular way you set up / store your config files when developing / deploying an

Hello, I''m running a Rails application which must sort and manipulate a lot of data which are loaded in memory. The Rails app runs on 2 mongrel processes. When I first load the app, both are 32Mb in memory. After some days, both are between 200Mb and 300Mb. My question is : is there some kind of garbage collector in Mongrel? I never see the two Mongrel processes memory footprint

I''m trying to do some initial benchmarking of our setup, mainly just to establish baselines. I''m essentially using the process Zed outlines in a previous message: http://rubyforge.org/pipermail/mongrel-users/2006-May/000200.html What I''m running into is that Mongrel appears only half as fast as Apache when serving a small static HTML file. If I then add in Apache with