similar to: Mongrel Web Server 0.3.11 -- Edge Rails and Win32 Compliant

Hello Folks, This is the big release of Mongrel that''s been in the works for a while now (well, like a week). It is chock full of changes and features, but mostly it syncs up the Win32 side of things, and validates that Edge Rails works without problems. It also features a more extensive and useful example of the GemPlugins called mongrel_config. First the usual stuff for people

I am not sure what i am doing wrong here, but no matter what i try i get no output from mongrel_config: $ mongrel_rails configtool $ telnet localhost 3001 Trying 127.0.0.1... Connected to localhost. Escape character is ''^]''. GET /config/ HTTP/1.1 HTTP/1.1 200 OK Connection: close Date: Tue, 19 Dec 2006 05:33:16 GMT Content-Type: text/html Content-Length: 0 Connection closed by

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:

I''d like to be able to type mongrel_rails start and have mongrel read a conf file like lighttpd does. I''m pretty sure this can be done but the documentation refers to a camping interface and I just don''t see it. Can someone point me in the right direction? Thx -- View this message in context: http://www.nabble.com/Mongrel%3A-Config-File-Q-t1535646.html#a4172243 Sent

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

Hi all I just went throught the docomentation of mogrel and I am wondering wht the plugins are good for. I understood how the work and I am comparing the situation to Lighttpd where mods are available for specific tasks. But in Lighttpd (or apache) those mods are running at native speed. But at mongrel, if the plugins are writte in ruby, couldn''t that code just be a rails plugin ? One

Hello everyone, Mongrel now has plugins that are based entirely on RubyGems. This feature was so slick that I decided to bust it out into a separate project called GemPlugin (more on that later). What the new plugin system does is makes it so that people can distribute Mongrel plugins as just plain gems, and mongrel will load them on the fly if people install them. There''s no

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

Hi list, I''m seeing a couple of issues with Mongrel. I''m running FreeBSD 6.1 and have previously been told that there are known conflicts between this and Mongrel, yet I hope these issues will be resolved with time. I''m overloading Mongrel with httperf on my local workstation. Mongrel is started directly with the mongrel_rails command and there is only one mongrel

Hi, Thanks Zed - this is very interesting. One item in particular caught my eye: Does anyone on this list have any comments or validation that Rails 1.2.1 is 2-4 times as slow as Rails 1.1.6? Topfunky provided a link that purports what looks like really horrible performance and memory characteristics for Rails 1.2.1, even v. 1.1.6:

I just moved from apache2/fcgi to apache2.2/mongrel and everything seems to work great except for 2 issues, one being major and one minor. the major issue i am experiencing is that after a period of time where my rails apps are not used, typically overnight, the mongrel processes become unresponsive. I currently have 3 apps running behind an apache2.2 proxy. every morning when i come in to

is there a way to determine how best to determine the number of mongrel processes to start? Right now i am running 2 in production but I see some people run about 8 or so. What is the cutoff and determening factor for this ? thanks adam -------------- next part -------------- An HTML attachment was scrubbed... URL:

hello all. ive come to the point where im thinking about deploying my ''rails on rails'' app-development solution built in camping. mainly, im wondering what the barriers to thread-safety are. for db, i use redland, and afaik it spawns a single db connection for each find, and keeps a pool around to reuse. iow, no ActiveRecord. are class-vars a problem? theres one that

I tried benchmarking the same site behind an NGINX proxy with both fastcgi and mongrel, and for some reason mongrel is performing pretty poorly in comparison. Any idea what I might be doing wrong? Here''s my benchmarks for 1 fcgi: Server Software: nginx/0.4.0 Server Hostname: eship.com.br Server Port: 80 Document Path: / Document Length: 95

Hi, I''m having fun playing around with Camping...I am slowly working on extending tepee to a personal e-notebook sort of tool (never lose my papers/revisions....hehe). I''ve given tepee an oswd css design, and am currently adding a admin page that I want to show the ruby version, sqlite version and db size and db stats information. I tried running: @db_stats =

Hello all, I''m new to Mongrel and am very impressed with what I see so far. This thing beats FastCGI hands down, and is even simpler to use than SCGI. Great job Zed! Thanks for all the hard work. I am a bit surprised at the memory usage patterns though. I''m not sure if I''m doing something wrong (most likely I am), or if this is a problem with the app I''m

Is this the behavior that supposedly indicates a problem with a particular action? Mongrel in development mode randomly hangs on random actions. Further requests cause USR1 logs like: Mon Sep 18 13:04:03 PDT 2006: 0 threads sync_waiting for /, 2 still active in mongrel. Mon Sep 18 13:07:52 PDT 2006: 1 threads sync_waiting for /public/stylesheets/table.css, 3 still active in mongrel. Mon Sep 18

Hi y''all, A prerelease of mongrel_cluster 0.1.3 is available for testing with the Mongrel 0.3.13 prerelease. This release contains bug fixes and adds a Ruby script for managing all applications on a server with a single command. To install: gem install mongrel_cluster --source=http:// railsmachine.rubyforge.org/releases/ Changes: * Suppress output from mongrel_rails. * Added a

Hello everyone, Mongrel now has plugins that are based entirely on RubyGems. This feature was so slick that I decided to bust it out into a separate project called GemPlugin (more on that later). What the new plugin system does is makes it so that people can distribute Mongrel plugins as just plain gems, and mongrel will load them on the fly if people install them. There''s no

Hi Everyone, I''m happy to announce the 0.2.0 release of Mongrel -- the fastest HTTP 1.1 library Ruby has yet. http://mongrel.rubyforge.org/ -- ruby docs lame page. http://rubyforge.org/projects/mongrel/ -- project page. Special thanks to Tom Copland for setting up my RubyForge goodness, and to Why for kicking in time to get the Camping examples up to snuff. This release should