What I’m trying to do here is just to provide the latest stable
binaries for someone who wants to deploy Rails. I dont intend to add a
GUI to start the system, neither to provide the auto config part. I
only bundle the binaries in an installer and it’s up to the user to do
all the configuration.
My 0.02:
I largely agree but I think that putting in some extra effort to do
configuration would be really helpful.
Ideally, the end user should be able to point to an existing Apache2
installation and put a line into the httpd.conf that sources default
configuration information from a file added to that installation by
your system. Appears Apache2 is too finicky because of the SCGI/
FastCGI stuff not being in by default. Maybe you should consider
doing it with lighttpd or even mongrel.
Looking at the directions your projects are taking, I’m beginning to
really like mongrel for its simplicity and would rather see that
becoming a really solid/stable product. Not that it isn’t getting
there already …
So am I, I like Mongrel too and its ease of use, configuration, maybe
we should consider releasing a setup kit pre configured to work with
Mongrel, such as Ruby, Rails, Lighttpd + Mod_proxy configure in load
balancer mode so you can have more instance of Mongrel running.
Hi, I’m working in “production mode” with Rails and Ruby on Win32
(mostly XP but a few 2k3 boxes).
I added the --cpu command to mongrel_rails_service to handle the cpu
affinity on dual/quad core machines.
Due the threading nature of ruby, we set fire 4 instances of mongrel,
each one “bound” to one processor, allowing us take better use of quad
opterons server we have here.
We use lighttpd + mod_secdownload + mod_proxy to provide secure download
of files, also load balancing.
So far that is our best setup.
I haven’t benchmarked them, so guess will do to get some comparisons
about performance.
I hope release in the following weeks a plugin and a series of scripts
and Rakefiles to simplify the bundling of your rails application with
these tools.
Regarding Compiling your own ruby, I have a updated, VC .NET 2003 (with
Platform SDK and the missing tools) all bundled in 14mb. Actually I sent
it to Zed S. to get mongrel-win32 gems corrently build with ruby 1.8.2
and 1.8.4 msvc6.
Ideally, the end user should be able to point to an existing Apache2
installation and put a line into the httpd.conf that sources default
configuration information from a file added to that installation by
your system. Appears Apache2 is too finicky because of the SCGI/
FastCGI stuff not being in by default. Maybe you should consider
doing it with lighttpd or even mongrel.
Yes that’s the issue with Apache, you cant guarantee the mod_fcgi or
mod_scgi binary you provide will work with the existing Apache build,
as for lighttpd, as I just said in a previous post, even so it’s
already built in I wasn’t able to get either to work on my setup,
maybe I should have another go.
I was thinking of Mongrel too but it’s too easy to install to bother
writing an installer for it really, Zed had already provided us with
the tools to make Mongrel configuration a joy.
Only issue with Mongrel is that you still to proxy it behind something
else if you want SSL support or more advanced web server functions
Looking at the directions your projects are taking, I’m beginning to
really like mongrel for its simplicity and would rather see that
becoming a really solid/stable product. Not that it isn’t getting
there already …
So am I, I like Mongrel too and its ease of use, configuration, maybe
we should consider releasing a setup kit pre configured to work with
Mongrel, such as Ruby, Rails, Lighttpd + Mod_proxy configure in load
balancer mode so you can have more instance of Mongrel running.