You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Антон Панков <an...@inbox.ru> on 2014/02/21 17:56:35 UTC
what to expect from fcgid
Dear All.
Please, explain what functionality now in trunk and what plans for
mod_fcgid. I miss FastCGIExternalServer feature.
The problem is to allow different site parts to be processed by
different FastCGI servers (frankly speaking, by different php-fpm
pools). Also, there is a need of external access
checker.
This type of configuration has the following problem with apache
2.4.X:
1. With mod_fastcgi and some magic [1] it is possible to achieve desired
configuration. But mod_fastcgi doesn't compile with Apache 2.4.
2. Mod_fcgid lack of FastCGIExternalServer feature.
3. Mod_proxy_fcgi has rough configuration. It can't be tied
to handlers, so it assigned to "directory", not to specified files.
Also, it avoid unix sockets (i know, they are in trunk),
So, the question is whether things that will help me already in
trunk? Does it make sense to wait for future apache httpd release?
May be i do things wrong and somebody can direct me to right way .
Appendices
1. Magic to run different
#----- PHP startup as unpriveleged user (general purpose script)-----
#-php-fpm (emptyfile) treat as a pipe to php-fpm standart pool
FastCgiExternalServer /var/fdwww/outroot/php-fpm -socket /var/run/fastcgi/php-fpm-common
FastCgiExternalServer /var/fdwww/outroot/php-fpm-wxsf -socket /var/run/fastcgi/php-fpm-common
# PHP regular fastcgi starter
Action php-fc /internal/doscript
Alias /internal/doscript /var/fdwww/outroot/php-fpm
#-------------BOX realm -------
#Accesschecker for BOX realm
FastCgiServer /usr/fdsys/acheckers/boxcheck.pl -processes 2
#PHP startup as boxscript user
#-php-fpm-box (emptyfile) treat as a pipe to php-fpm boxscript pool
FastCgiExternalServer /var/fdwww/outroot/php-fpm-box -socket /var/run/fastcgi/php-fpm-box
# PHP magic for Box starter
Action php-fc-box /internal/doscript-box
Alias /internal/doscript-box /var/fdwww/outroot/php-fpm-box
--
Best regards,
Anthony mailto:ant_mail@inbox.ru
Re: what to expect from fcgid
Posted by Anthony Pankov <an...@inbox.ru>.
>>https://github.com/hollow/mod_fastcgi_handler
Yes, this kind of configuration is what i want.
I think this link usefull for Kean Johnston, who is gathering to
please us with mod_extfcgi.
> https://github.com/hollow/mod_fastcgi_handler is quite easy to
> configure, unfortunetly it is abandoned
> 2014-02-21 17:56 GMT+01:00 Антон Панков <an...@inbox.ru>:
>> Dear All.
>>
>> Please, explain what functionality now in trunk and what plans for
>> mod_fcgid. I miss FastCGIExternalServer feature.
>>
>> The problem is to allow different site parts to be processed by
>> different FastCGI servers (frankly speaking, by different php-fpm
>> pools). Also, there is a need of external access
>> checker.
>>
>> This type of configuration has the following problem with apache
>> 2.4.X:
>>
>> 1. With mod_fastcgi and some magic [1] it is possible to achieve desired
>> configuration. But mod_fastcgi doesn't compile with Apache 2.4.
>>
>> 2. Mod_fcgid lack of FastCGIExternalServer feature.
>>
>> 3. Mod_proxy_fcgi has rough configuration. It can't be tied
>> to handlers, so it assigned to "directory", not to specified files.
>> Also, it avoid unix sockets (i know, they are in trunk),
>>
>> So, the question is whether things that will help me already in
>> trunk? Does it make sense to wait for future apache httpd release?
>>
>> May be i do things wrong and somebody can direct me to right way .
>>
>>
>> Appendices
>> 1. Magic to run different
>> #----- PHP startup as unpriveleged user (general purpose script)-----
>> #-php-fpm (emptyfile) treat as a pipe to php-fpm standart pool
>> FastCgiExternalServer /var/fdwww/outroot/php-fpm -socket /var/run/fastcgi/php-fpm-common
>> FastCgiExternalServer /var/fdwww/outroot/php-fpm-wxsf -socket /var/run/fastcgi/php-fpm-common
>>
>> # PHP regular fastcgi starter
>> Action php-fc /internal/doscript
>> Alias /internal/doscript /var/fdwww/outroot/php-fpm
>>
>> #-------------BOX realm -------
>> #Accesschecker for BOX realm
>> FastCgiServer /usr/fdsys/acheckers/boxcheck.pl -processes 2
>> #PHP startup as boxscript user
>> #-php-fpm-box (emptyfile) treat as a pipe to php-fpm boxscript pool
>> FastCgiExternalServer /var/fdwww/outroot/php-fpm-box -socket /var/run/fastcgi/php-fpm-box
>> # PHP magic for Box starter
>> Action php-fc-box /internal/doscript-box
>> Alias /internal/doscript-box /var/fdwww/outroot/php-fpm-box
>>
>> --
>> Best regards,
>> Anthony mailto:ant_mail@inbox.ru
>>
--
С уважением,
Anthony mailto:ant_mail@inbox.ru
Re: what to expect from fcgid
Posted by Lazy <la...@gmail.com>.
https://github.com/hollow/mod_fastcgi_handler is quite easy to
configure, unfortunetly it is abandoned
2014-02-21 17:56 GMT+01:00 Антон Панков <an...@inbox.ru>:
> Dear All.
>
> Please, explain what functionality now in trunk and what plans for
> mod_fcgid. I miss FastCGIExternalServer feature.
>
> The problem is to allow different site parts to be processed by
> different FastCGI servers (frankly speaking, by different php-fpm
> pools). Also, there is a need of external access
> checker.
>
> This type of configuration has the following problem with apache
> 2.4.X:
>
> 1. With mod_fastcgi and some magic [1] it is possible to achieve desired
> configuration. But mod_fastcgi doesn't compile with Apache 2.4.
>
> 2. Mod_fcgid lack of FastCGIExternalServer feature.
>
> 3. Mod_proxy_fcgi has rough configuration. It can't be tied
> to handlers, so it assigned to "directory", not to specified files.
> Also, it avoid unix sockets (i know, they are in trunk),
>
> So, the question is whether things that will help me already in
> trunk? Does it make sense to wait for future apache httpd release?
>
> May be i do things wrong and somebody can direct me to right way .
>
>
> Appendices
> 1. Magic to run different
> #----- PHP startup as unpriveleged user (general purpose script)-----
> #-php-fpm (emptyfile) treat as a pipe to php-fpm standart pool
> FastCgiExternalServer /var/fdwww/outroot/php-fpm -socket /var/run/fastcgi/php-fpm-common
> FastCgiExternalServer /var/fdwww/outroot/php-fpm-wxsf -socket /var/run/fastcgi/php-fpm-common
>
> # PHP regular fastcgi starter
> Action php-fc /internal/doscript
> Alias /internal/doscript /var/fdwww/outroot/php-fpm
>
> #-------------BOX realm -------
> #Accesschecker for BOX realm
> FastCgiServer /usr/fdsys/acheckers/boxcheck.pl -processes 2
> #PHP startup as boxscript user
> #-php-fpm-box (emptyfile) treat as a pipe to php-fpm boxscript pool
> FastCgiExternalServer /var/fdwww/outroot/php-fpm-box -socket /var/run/fastcgi/php-fpm-box
> # PHP magic for Box starter
> Action php-fc-box /internal/doscript-box
> Alias /internal/doscript-box /var/fdwww/outroot/php-fpm-box
>
> --
> Best regards,
> Anthony mailto:ant_mail@inbox.ru
>
Re: mod_fastcgi and Apache 2.4 (Re: what to expect from fcgid)
Posted by "Mikhail T." <mi...@aldan.algebra.com>.
On 21.02.2014 13:59, Anthony Pankov wrote:
> Thank you for suggestion.
> But this packet does not install "from box" in
> FreeBSD. It does not install via "apxs -cia" also. Besides that
> there is a patch for mod_fastcgi in FreeBSD ports that doesn't seem
> trivial.
Unless apache@FreeBSD.org team comes up with a good reason to the contrary, the
mod_fastcgi port will be buildable with either 2.2 or 2.4 apache in a week or so
-- the PR addressing the problem was submitted last summer.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/179710
Meanwhile, you can test the update offered on the above ticket (second diff).
Barring show-stopping feedback, that's what will be committed to the port.
For more FreeBSD-specific questions about Apache, please contact
apache@FreeBSD.org (and/or myself) -- not this list. Yours,
-mi
Re: mod_fastcgi and Apache 2.4 (Re: what to expect from fcgid)
Posted by Anthony Pankov <an...@inbox.ru>.
Thank you for suggestion.
But this packet does not install "from box" in
FreeBSD. It does not install via "apxs -cia" also. Besides that
there is a patch for mod_fastcgi in FreeBSD ports that doesn't seem
trivial.
> On 21.02.2014 11:56, Антон Панков wrote:
>
> But mod_fastcgi doesn't compile with Apache 2.4.
>
> This is entirely possible, actually -- and has been for a
> while. Pathes exist and are maintained:
>
> https://github.com/ByteInternet/libapache-mod-fastcgi
>
> Yours,
>
> -mi
>
>
--
С уважением,
Anthony mailto:ant_mail@inbox.ru
mod_fastcgi and Apache 2.4 (Re: what to expect from fcgid)
Posted by "Mikhail T." <mi...@aldan.algebra.com>.
On 21.02.2014 11:56, ????? ?????? wrote:
> But mod_fastcgi doesn't compile with Apache 2.4.
This is entirely possible, actually -- and has been for a while. Pathes exist
and are maintained:
https://github.com/ByteInternet/libapache-mod-fastcgi
Yours,
-mi
Re: what to expect from fcgid
Posted by Kean Johnston <ke...@gmail.com>.
On 2/24/2014 1:23 PM, Anthony Pankov wrote:
>
> It is very interesting. Especially if it is possible to associate
> FastCgi servers(socket) with apache handlers and then use handlers where
> needed as SetHandler/AddHandler.
Yes you can indeed do that.
> Also i'm glad to hear that mod_extfcgi will not cross mod_fcgid
> functionality.
That is very much by design. I want it to *only* deal with FastCGI, not to
bolt on a process manager as well. I have always felt the process
management for the FastCGI application servers were best left to outside of
the Apache core, if for no other reason that it is common for people to
have mixed nginx/Apache setups and both should be able to use the FastCGI
applications.
Also, to be honest, a huge percentage of people that want FastCGI will be
using it for PHP, and php-fpm does its own process management.
Kean
Re: what to expect from fcgid
Posted by Anthony Pankov <an...@inbox.ru>.
It is very interesting. Especially if it is possible to associate
FastCgi servers(socket) with apache handlers and then use handlers where
needed as SetHandler/AddHandler.
Also i'm glad to hear that mod_extfcgi will not cross mod_fcgid
functionality.
I can try it on development server (FreeBSD). But my skill may be not
enough to compile it.
> On 2/21/2014 6:56 PM, Антон Панков wrote:
>> Dear All.
>>
>> Please, explain what functionality now in trunk and what plans for
>> mod_fcgid. I miss FastCGIExternalServer feature.
> I am in the final stages of testing a new FastCGI module, written for 2.4
> (although it MAY work on 2.2) called mod_extfcgi. It *only* deals with
> external FastCGI application, it has absolutely no process management, as
> that is best left to dedicated code for that purpose.
> It supports both TCP and UNIX sockets, it does authn and authz and, unlike
> any other FastCGI module Ive seen so far, it supports the FastCGI "FILTER"
> role. I also think it's fairly easy to configure but then, I would :)
> I want to do some more testing and clean up the documentation before I
> publish it on github but I should get that done during the course of the
> next week if you want to play with it when it's done.
> Hope that helps.
> Kean
> PS in the interestes of full disclosure this is my first Apache module so
> there may well be some rough edges, I am eagery looking forward to more
> expert eyes critiqueing it.
--
С уважением,
Anthony mailto:ant_mail@inbox.ru
Re: what to expect from fcgid
Posted by Kean Johnston <ke...@gmail.com>.
On 2/21/2014 6:56 PM, Антон Панков wrote:
> Dear All.
>
> Please, explain what functionality now in trunk and what plans for
> mod_fcgid. I miss FastCGIExternalServer feature.
I am in the final stages of testing a new FastCGI module, written for 2.4
(although it MAY work on 2.2) called mod_extfcgi. It *only* deals with
external FastCGI application, it has absolutely no process management, as
that is best left to dedicated code for that purpose.
It supports both TCP and UNIX sockets, it does authn and authz and, unlike
any other FastCGI module Ive seen so far, it supports the FastCGI "FILTER"
role. I also think it's fairly easy to configure but then, I would :)
I want to do some more testing and clean up the documentation before I
publish it on github but I should get that done during the course of the
next week if you want to play with it when it's done.
Hope that helps.
Kean
PS in the interestes of full disclosure this is my first Apache module so
there may well be some rough edges, I am eagery looking forward to more
expert eyes critiqueing it.