similar to: Graceful stop in, timeouts out (for now)

Hey, I did some pre-compiled gems for both Mongrel and win32 service, wrote some quick instructions, and threw everything onto a (Mongrel hosted) temp site. Please go hit: http://zedshaw.homelinux.org:3000/files/win32_howto.html And give the instructions a shot. Luis should have the stuff moved around and then we''ll have a nice clean install and set of instructions for all this. Any

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

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

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

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

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

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

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

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

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

Hi All I am using version 0.3.13.3 and since there is no logging support for win32 application. I was wondering if it was possible to get any kind of logging at all. I have tried to these two options 1. Stream redirection using "mongrel_rails start -c C:/myspace/snapshot -p 4111 -t 70 -e production -P log/mongrel-1.pid > C:\temp\mongrel-1.log" The console print the output stream

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

Hey Zed- I had a user with an app that was leaking memory with mongrel but not lighty/fcgi. I have been doing anything I can to track it down. I already did the Mutex patch to use unshitf and pop instead of shift and push and it didn''t really help much. The mem leak only really shows up when you use the wsess option to httperf. The other day I saw a ruby C extension that

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

Hello Guys, I''ll like to suggest a small release fix before we start doing big changes: platform fixes. Current we''re setting MSWIN32 (mswin32) as platform for Windows gem, but we should be using Gem::Platform::CURRENT instead (i386-mswin32 as current Ruby windows implementation). Also, the jruby/java platform need to be defined. That change will ease the compatibility path

Hey Guys. I just updated a project form 1.1.4 that was working with autotest 3.10 without issues: 1) Updated spec/model/project_spec.rb and it fired only that spec. 2) Updated app/model/project.rb and it fired only the matching spec file. After the update of rspec and rspec-rails as plugins a few minutes ago, it only run the controller specs and no other. Also, it doesn''t matter which

Hi Zed, I checked in a pure-Ruby URI classifier to Mongrel trunk. Ola''s Java port of the TST had some bug, and I don''t think it''s necessary in the first place. The Ruby classifier is around 25 lines instead of the 400-odd lines for the C extension and the 200-odd for the Java extension. It uses a Regexp which is perhaps shady: @matcher = Regexp.new(routes.map do

Hello Mongrel Users, I''m writing a web server called Ebb. It''s written in C, makes use of the Mongrel HTTP parser, and uses libev its event loop. The goal is to be small, fast, and language independent server that can host web frameworks. I have written a small Ruby binding which provides a Rack handler - this will allow Ebb to host Rails, Merb, and other Ruby frameworks. In the

Bugs item #16700, was opened at 2007-12-30 02:04 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=411&aid=16700&group_id=85 Category: win32-api Group: Packaging Status: Open Resolution: None Priority: 3 Submitted By: Luis Lavena (luislavena) Assigned to: Nobody (None) Summary: 1.0.5 x86-mswin32-60 gem is broken Initial Comment: Daniel, The gem you have