I’ve had nothing but smooth sailing with mod_fastcgi and apache 2.0.x. I
would not advise going straight to 2.2 because it broke some modules and
porters in the Linux and BSD worlds are still playing catch-up. If
you’re using debs, RPMs or some other form of package for your Apache
and modules, you may want to get the latest packages if there are any
newer than what went out with the distro. In my FreeBSD world, some
crucial patches that made mod_fastcgi build properly hit in January and
you may find something similar on Debian, since fastcgi module
maintenance got back in gear around that time.
If you’re planning on hosting an SVN server on the same box, Apache 2.0
is the obvious sensible choice because the SVN Apache modules require
2.x. It’s quite a bit easier to set up SVN clients talking to an
HTTP/HTTPS repository than it is the other ways involving ssh.
Eric B. wrote:
I am just installing a new test environment, but this is just for
preparing the next one, which will be a production server.
I am doing a clean Debian Sarge 3.1 install with stable sources. I have
to decide if I install Apache 1.x or 2 now.
I have read that FastCGI is better supported/developed for Apache 1.x.
Is this (still) true? What is easier, more stable, etc? I want to run
rails with Apache/FastCGI then. (Or is there an even better solution
which I am not aware of?)
Any suggestions, experiences, hints?