On Wed, Jan 19, 2005 at 03:45:11PM +1100, Adam Kennedy wrote: > > When RT3 is installed on an Apache2 debian box, fastcgi is not avaible > and SpeedyCGI would appear to not work with the mods-available layout, > leaving the Apache2 config as the only option.
There is a libapache2-mod-fastcgi package, just like libapache-mod-fastcgi it is in non-free/web. There is currently no speedycgi apache2 module packaged for Debian though. > This server interface requires that mod_rewrite is both installed an > enabled, otherwise restarting apache fails. > > When installing on an Apache 2 set up, the RT3 install should enable > mod_rewrite. We do make it very clear in the installation instructions that mod_rewrite is required for the default config files provided and we also note how to go about doing that with Apache2. There are many problems which leave me feeling that we cannot automatically enable mod_rewrite for Apache2. We have no way of knowing at installation time whether the user intends to use our package with Apache2 or Apache1.3 (they may have both installed). Also the user may have deliberately chosen to disable mod_rewrite. Some users may not appreciate us enabling mod_rewrite for them before they have had a chance to configure rt3 and apache2 in the way they want. They may have chosen not to use the default config files we provide, they are only one very limited way, out of many ways, of configuring apache to serve rt3. There is also the issue of detecting how someone has configured apache2, at my work we do not use the mods-available and mods-enabled directories system at all. We prefer to have everything in one file to ease configuration file control. I hope that explains why we do not automatically enable apache modules. Stephen Quinney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
