Another thing I remember tripping me up, is even if you have fastcgi support
enabled, it may not have more precedence than conventional CGI support, so
you should delete/rename dispatch.cgi so that dispatch.fcgi is loaded
instead. This is also a quick way to find out if your fast cgi install
worked.
On Tue, Apr 1, 2008 at 4:23 PM, Corey Van Allen <[EMAIL PROTECTED]> wrote:
> To answer my own question, in case it helps anyone else. Here are the
> steps I took to increase apache's performance.
>
> 1. Install libfcgi-ruby1.8. ('gem install fcgi' may work for you)
>
> 2. Edit tracks/public/.htaccess as follows
> diff .htaccess-new .htaccess-org
> 3,4c3,4
> < AddHandler fcgid-script .fcgi
> < #AddHandler fastcgi-script .fcgi
> ---
> > # AddHandler fcgid-script .fcgi
> > AddHandler fastcgi-script .fcgi
> 34c34,35
> < RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
> ---
> > RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
>
> 3. Edited mod_fcgid.conf as follows
> <IfModule mod_fcgid.c>
> AddHandler fcgid-script .fcgi
> SocketPath /var/lib/apache2/fcgid/sock
> SharememPath /var/lib/apache2/fcgid/shm
> IPCConnectTimeout 20
> IPCCommTimeout 40
> DefaultInitEnv RAILS_ENV production
> IdleTimeout 60
> ProcessLifeTime 6000
> MaxProcessCount 32
> DefaultMaxClassProcessCount 2
> </IfModule>
>
> 4. Restarted apache and tracks is much faster now.
>
> --
> Corey
> _______________________________________________
> Tracks-discuss mailing list
> [email protected]
> http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
>
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
