similar to: Temporary win32 gems up.

Ok, I have checked in the first draft of rails win32 service into examples mongrel_rails_service is the controller, and the _svc script is actually the service. The controller uses Mongrel Commands as requested by Zed, but the service was simplified for debugging purposes, later will merge and refactor both files. The environment defaults to production, so if wanted to run it on other, you must

Hey Luis, Just implemented the first cut at a graceful stop setup. It seems to mostly work except for a few hicups here and there which I''ll test out. I''ve tested this under OSX and will test on the other platforms soon. To use it take a look at the examples/simpletest.rb and see how I setup an "INT" handler to call HttpServer.stop. Hopefully this will help with

Hi folks, I''ve been working on the plugins system this weekend and I think I''ve nailed it down. The system will basically be able to load gems that are configured right to be plugins. It''ll do it fairly dynamically and shouldn''t require any configuration from the end user other than to install the gem. Doing this though will involve a bit of surgery on the

This patch: - adds --prefix option to service::install in mongrel-service plugin - fixes bug with config values merging in the service - enables gemplugins in the service. Questions: - why the load_plugins command was commented out? It seems working for me. - why bin/mongrel_rails_service and bin/mongrel_rails_svc still in the main package? - a lot of code is duplicated in both versions

Hello Everyone, Just a small announcement for Mongrel 0.3.12.4 which fixes the following things: * Corrects the date format returned so that months are three chars only. * Fixes a problem where DirHandler wasn''t returning Last-Modified and Etag headers for unknown MIME types. * Implements a default mime type for anything it doesn''t know about, and lets you set it via an

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

Hello Folks, This release of Mongrel should make the win32 folks go crazy. Thanks to Luis Lavena it supports a full service system for installing any Rails app as a service. This lets you start your rails apps from either the command line or the Service console. Stopping is still a bit problematic but we hope to have that solved in the next release. You win32 folks should probably send Luis

Ok, this might sound bad... well, actually it is. I''m my rewrite of mongrel_rails_service and provide a uniform set of commands in the line of gem_plugin commands, found a few issues while stopping the service. Thinking that rails (1.1.2) was responsable, tested against my 1.0.0 rails app, both with the same results. Again, reverted to mongrel 0.3.8, when services was working ok, with

Hi there what''s the status of the 0.13.4 release on Windows? I want to wrap up a project in the next 2 weeks and I''d wait for the new release if it''s coming in that timeframe. Otherwise I''d stay with the current windows version. thanks Jens-Christian Fischer

Hello Mongrels around the world! Been thinking a way to unify the issue I described in the subject. For those who aren''t aware, mongrel (actually, mongrel_rails) only generate the log file if daemonize was used (-d) That means no log file under windows, due his lack of fork/daemonization capabilities. Now, users that need to run mongrel on windows cannot report and fill the empty

Hello Everyone, Mongrel is due for a 0.3.12 release which will feature some pretty insane goodies for everyone. There''s talk of IOWA support, lots of speed improvements (including sendfile support), a great Configurator which makes configuring Mongrel a snap (especially for framework implementers), and a ton of debugging stuff. WARNING This is a pre-release announcement for the

Hey so, People are asking about Mongrel Ruby 1.9 compatibility. Isn''t the point of 1.9 for library developers to have time to get ready for 2.0? It''s not like 1.9 is a production release. Evan -- Evan Weaver Cloudburst, LLC

Hello mailing list! (Ehhh, that sounds a bit silly, don''t you think?) Anyway, I''m glad that Zed allow me contribute to this project. Been using Ruby and Rails for half-year and lot of things I have learned running on win32 arena, that I wanted to share with everybody. As previously post on ruby-talk by Zed, I will create the scripts that made posible run mongrel as services

Hello Guys, I''m reviewing the code for 1.9, and forgot about this when we first spoke on this subject. The current way we stop threads is using Thread#raise to spread StopServer exception, which will not work as expected in 1.9. 1.9 will treat raised exceptions as #kill, like JRuby does, so the worker threads will not finish serving the client and _then_ exiting, but will be

Dear Mongrels, The same questions keep coming up over and over on the list, which is ok, but not really optimal. If we added a wiki to the Mongrel site to handle FAQs, what wiki should it be? Required features would be: * Spam protection * Doesn''t look shitty I would probably spring for Trac (and also migrate the bugtracker) if noone else has opinions, but I''m sure some of

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 Everyone, Just a quick message to say that I''m holding back the 0.3.7 release so I can get this flexible plugin system going that we''ll need for the next step of loading user defined handlers and filters. What I''ve done is completely replaces pluginfactory with an alternative that lets you create simple classes like so: class Stop < Plugin "/commands"

I''m doing another 0.3.7 release this weekend which will roll in changes from Luis for the win32 service, and some enhancements to the mongrel_rails Unix runner which makes it behave better with switchtower. There''s also a new document on setting up a proxy with lighttpd to do simple clustering on the site: http://mongrel.rubyforge.org/docs/lighttpd.html I''ll be

Hi list, I downloaded and tried to install Mongrel (latest stable version) from the -win32 gem. Platform is Win2K. It said it needed daemons so got and installed that. Then it said it needed cgi_multipart_eol_fix (I think that was the name, not at my machine now, can confirm later and repost if needed). Googled for that but couldn''t find it. (Don''t have net connectivitity for a

Hi all, Ruby 1.8.4 Rails 1.1.2 Mongrel 0.3.12 I''m seeing this output from the Mongrel server: Client closed socket requesting file C:/eclipse/workspace/dslscheduler/public/javascripts/prototype.js: Invalid argument It seems to be harmless, but I''m curious as to what''s causing it. Any ideas? Thanks, Dan