up vote 0 down vote favorite
share [g+] share [fb]

I've developed Python application, which operates as FastCGI service. I've tested it under nginx and it worked OK. The FastCGI service is external, I run it via spawn-fcgi. nginx config was:

location / {
    fastcgi_pass   127.0.0.1:9000;
    fastcgi_param  QUERY_STRING       $query_string;
    fastcgi_param  DOCUMENT_URI       $document_uri;
    fastcgi_param  SERVER_NAME        $server_name;
    fastcgi_param  SERVER_PROTOCOL    $server_protocol;
    fastcgi_param  SERVER_PORT        $server_port;
    fastcgi_param  REQUEST_METHOD     $request_method;
    fastcgi_param  REMOTE_ADDR        $remote_addr;
}

Now I need to use my FastCGI service under Apache2. The mod_fastcgi for Apache is already configured. I cannot configure the VirtualHost to transfer all of requests to FastCGI (as it was in nginx).

I tried the following config:

<VirtualHost *:80>
    ............
    FastCgiExternalServer / -host 127.0.0.1:9000
</VirtualHost>

But this is not working.

Please, could you show me the working config for external FastCGI service.

link|improve this question
2  
Is FastCGI a must? using mod_wsgi with apache2 will give you much higher performance and less headache of setup and maintaining code.google.com/p/modwsgi – number5 Dec 7 '11 at 13:15
Unfortunately, I cannot use mod_wsgi because I already have mod_python installed, and these 2 modules are incompatible, as far as I understood. – Igor Semenov Dec 8 '11 at 12:45
Then you should continue to use mod_python. There are very few people actually using fastcgi for python these days. – number5 Dec 9 '11 at 2:39
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.