similar to: [OFF-TOPIC] SCGI now maintained by Jeremy Evans

Hello Everyone, Been head down with personal stuff, but I wanted to shoot out this email saying that I''ve collected the list of volunteers and decided that I''d just hand the keys over to them and see how they do. The list of people I have so far is: Ezra Zygmuntowicz <ezmobius at gmail.com> "Kirk Haines" <wyhaines at gmail.com> "Wayne E. Seguin"

Ok, my little experiment proved my point. Ruby 1.8.6 is not viable for production. Requiring it and dropping the cgi fix back patch isn''t an option. It''s not even clear whether the latest 1.8.6 has any remaining fixes. So, crisis averted. Mongrel WILL NOT require 1.8.6 and now I''m going to dig out where these security fixes are coming from and how to host this kind

This is a proposed patch for the security hole reported today. You can just add the test for @path being at index 0 in the exanded req_path as shown below. Take heed of the comment I''ve added too, and there was a test for this very attack in the unit test suite, so it was removed by someone as well. I didn''t test this but I''m pretty sure it''s the fix. ===

This is stupid, I made Luis, Wayne, Evan, and Filipe admins. Make anyone else admins that you want and do all the changes you need. Especially since you guys are mostly running the show anyway. -- Zed A. Shaw - Hate: http://savingtheinternetwithhate.com/ - Good: http://www.zedshaw.com/ - Evil: http://yearofevil.com/

Hi, I kept getting a very weird question about Mongrel (http://mongrel.rubyforge.org) and SCGI that I think really needs to be cleared up: ** Mongrel is not SCGI and will never need, use, require, or interact with SCGI (unless someone wants to write the handler for it). ** For some reason people have been under the impression that Mongrel actually uses or interacts with my other project SCGI

Hopefully that gets everyone''s attention. Evan Weaver has whined enough to make me do a release to change the requirements on the Mongrel gem so that it doesn''t need the cgi_multipart_eof_fix anymore. *************************** THIS ALSO MEANS THAT MONGREL WILL HAVE TO REQUIRE RUBY 1.8.6 OR GREATER! NO EXCEPTIONS! *************************** I know Debian guys like to hack

Hi All, Alright, this release is getting closer. It''s nearly complete except the docs on my site aren''t written yet. There is however a full README with RDoc documentation and several packages including a gem release. Please check out the latest release at: * Announcement: http://www.zedshaw.com/ * README and RDoc:

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

Hello Rails Folks, This is just a quick announcement to let people know that SCGI Rails Runner now has a RubyForge project at: http://rubyforge.org/projects/scgi/ There''s already a few bug and feature requests there and I''ll be quickly putting more docs online as well as a new release shortly. The latest source is checked into subversion if you are interested in

Hey folks, I''m falling behind in my Mongrel duties and seriously need to recruit an enterprising individual to take on the patch queue and help push out a new release with some minor fixes. The goal would be to just get patches that are currently languishing, pull them together, put them in the source, write some tests to try them, and then one slight design change. If this works out

Hi, I''ve had several reports of people with problems using lighttpd 1.4.1 or 1.4.2 with my recently released SCGI Rails runner. I''ve been testing these versions of lighttpd and I see the following problems: 1. When run with -D option, a CTRL-C will often times give a segfault. This is linux for me, any others? It most often happens right after try an SCGI handled request.

Hi Folks, I believe I tracked down the problem with the leaked DB connections. The simple fix is to put: ActiveRecord::Base.threaded_connections = false In your environment.rb file right before environment.rb does any ActiveRecord use. For example, here''s mine: ActiveRecord::Base.threaded_connections = false ActiveRecord::Base.configurations =

two problems, pls help...I''m under big pressure at work to fix this! I''m having trouble getting scgi and lighttpd running on windows - here''s what I did: On Win XP, I installed ruby, rubygems, and setup my rails app. All works fine with webrick. I then did: gem install cmdparse and gem install highline (as required for the scgi_rails gem according to

And now it''s time for yet another Mongrel release. Mongrel is a small fast HTTP library written in (partly) Ruby. It is intended to be used by web app framework authors to make their applications fast and deployable without resorting to SCGI/FastCGI trickery. Mongrel is tested to work on Linux and Mac OS X (with more reports welcome). You''ll need a full compiler to

Hi, While learning Ruby and Rails, I decided I just as well learn Linux along the way... It''s been fun, but I''m stuck at one of those exasperating moments... I hope someone can help me :) I installed Ruby 1.8.4 on Fedora Core 4, then Rails, then lighty, and then SCGI. I used yum to install lighty... and it already comes with mod_scgi. I created my first application in

Hi, So thanks to Zed I was able to get lighty/scgi and a Rails app running. I know this might not be the best place to post this, but I guessed there may be several others with similar experiences here. So, the following step is to have several apps each in its on subdirectory. I tried the following to no avail: $HTTP["url"] =~ "^/tango/" { server.document-root =

samba@samba.org Serge Gavrilov <serge@pdmi.ras.ru> Ed Schernau <ed@schernau.com> Jeremy Allison <jeremy@valinux.com> Cristian POP <cpop@compas.dntcj.ro> Ed Schernau <ed@schernau.com> John Evans <samba@kilnar.com> David Bullock <davidb@loftuscomp.com.au> Gunnar Lindholm <gunnar.lindholm.320@student.lu.se> Junaid Iqbal

[ERR][17968] Handling client: can''t convert nil into String Hi, We decided to go with SCGI + Lighttpd for Rails at our company and had no problems with the initial setup. Everything ran fine and was fast. However, problems occurred when we tried to rebuild Lighty with SSL capabilities. With this build, even with SSL off in the config file the application fails on the first request.

Hi, I have an application running on Apache SCGI (Win XP). Once I run it in production mode (scgi_ctrl config -S -e production ) I''m getting stack trace instead of HTTP status 500 (Application Error) and the error is logged production.log. The application works fine without SCGI. Your help is highly appreciated.... Thanx /* production.log */ # Logfile created on Thu Jan 04 16:35:43

Hi Everyone, I figured out this weekend that Ruby''s Thread implementation causes the Ruby/Event binding I wrote to completely stall and go dead. After reviewing the Ruby source and watching several strace runs, it''s clear that the Ruby Thread implementation uses select in a way that--while not being bad--just isn''t compatible with libevent. The second a thread is