On Thu, May 8, 2014 at 7:54 AM, Zeev Suraski <[email protected]> wrote:
> On 8 במאי 2014, at 17:37, Andrea Faulds <[email protected]> wrote:
>
>
> On 8 May 2014, at 15:29, Ferenc Kovacs <[email protected]> wrote:
>
>
> I think this actually shows how little understanding there is in the market
> in terms of how easy migrating to FastCGI is.
>
>
> setting up fastcgi is a bit more complicated for the less tech savy people.
> it adds another step of indirection, stuff like using mod_fcgid or
> mod_fastcgi, using unix sockets or tcp, setting up the correct timeout
> settings through the pipe, max request length, etc.
>
>
> It’s also easier for new users to configure it wrong. A lot of servers have
> been misconfigured with FastCGI and have PATH_INFO-related exploits. You
> can’t make the same mistake with mod_php.
>
>
> But all of this is very manageable. Distros and stacks (which is what the
> vast majority of users use, especially new users) will have the right setup
> out of the box. To the average new user it'll work just as it did before,
> non extra setup needed.
>
> Heck, we can even get "make install" to work properly with Apache FastCGI
> if we wanted to, and create a base setup that's fast and secure.
Could you spend a day or two on that please?
And then document the crap out of fpm?
That can even be part of 5.6 and will be one of the major things we
can announce.
The current installation instructions of PHP have barely changed at
all in the past 10 years, other then tiny maintenance tweaks here and
there. That sucks balls. And means fcgi and fpm are poorly documented.
That means people will just follow what they are used to and know,
since every single installation instruction ever talks about mod_php
anyway.
If you can help us spend some time on making fpm more inviting for
people, make the installation easy flowing - and with some tweaks to
"make install" we are golden.
-Hannes