Re: [Fastcgipp-users] fastcgi++ over a persistent unix domain socket?

[Volker Schreiner]

Hi J.M.,

i am running a web application that was developed under the use of
fastcgi++ and gets connected by the
nginx webserver. To start the web application process i am using the
programm spawn-fcgi that can be
configured to use an unix socket connection as well as an network socket.

spawn-fcgi -u webapp -g webgrp -G www-data -U www-data -s
/tmp/webapp.socket -f /usr/bin/webapp

The above example starts the binary /usr/bin/webapp with the rights of
the user webapp and the group webgrp and
creates a unix socket named /tmp/webapp.socket that can be connected by
the nginx server.

best regards

Volker

Am 27.09.2010 04:45, schrieb Langevin:
> hi all,
>
> i'd like to make a fastcgi++ based web application to work with the
> nginx http server.
> the nginx doc (1) says that nginx will not start my application (as some
> other http servers do) and that i should start it separately and have it
> listen on a socket.
> i did get that to work with the stock fastcgi library (2), but not with
> fastcgi++
> from my understanding of the class reference, i would have to provide
> the file descriptor id of a socket as argument to the constructor of
> Fastcgipp::Manager. I didn't get that to work.
> So i was wondering: do you guys have any working example code that would
> show how to do that?
>
> i.e. a simple fastcgi++ program that would open a named socket and use
> it to communicate with the web server (who knows the path of the socket
> where my app is listening)?
>
> Best Regards,
> J.M.
>
>