Re: Directives in Apache

Emil A Eklund wrote:
> FactCgiConfig is used to set the default parameters, such as connection 
> and idle timeout. Whatever is specified using this directive applies to 
> all fast cgi instances. It's not required but can come in handy if the 
> same directive is to be applied to more than one instance.

This is a great write up.  Thank you.

As an example of how to use FastCgiConfig I currently have an entry of
<IfModule mod_fcgid.c>
   AddHandler fcgid-script .fcgi
   SocketPath /var/lib/apache2/fcgid/sock
   IPCConnectTimeout 20
</IfModule>

Would I modify this (eg to add an autoupdate option for development) by adding 
the line identified by '<<<<<'.

<IfModule mod_fcgid.c>
   AddHandler fcgid-script .fcgi
   SocketPath /var/lib/apache2/fcgid/sock
   FastCgiConfig -autoUpdate                 <<<<<
   IPCConnectTimeout 20
</IfModule>

Regarding the other settings.  These are good descriptions of what the do.  It 
seems to me that the ruby development community is having an fcgi revival 
because it plays well with Rails.  But considering how many people are citing 
the use of fcgid over mod_ruby or cgi, I'm surprised at how little there is on 
the internet regarding this whole technology.  It seems like a really great way 
to run

To better understand what's under the hood, so that I can impliment these 
various types of FastCgi application, would it make sense to go through the 
whitepapers or is there other recommended reading.

> FastCgiConfig defines a dynamically handled fastcgi instance, that is 
> the application will be started and handled by the web server (actually 
> by the fastcgi module's process manager), if it goes down a new instance 
> will be started.
> 
> The following will define /var/web/fcgiappname as a fastcgi instance, it 
> will be started with the environment variable NAME set to value and be 
> exposed as /app.
> 
> FastCgiServer /var/web/fcgiappname -initial-env NAME=value
> ScriptAlias /app /var/web/fcgiappname
> 
> FastCgiExternalServer on the other hand defines an external fastcgi 
> instance,the application will not be either started or handled 
> automatically, that's up to the user, hence the name external.In this 
> case the web server/fastcgi module will act like a proxy and forward all 
> suitable requests to the server.
> 
> FastCgiExternalServer /app -host localhost:4080 -initial-env NAME=value
> ScriptAlias /app /app

This last one is very cool!!
___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/