On Thu, Nov 5, 2026 at 12:06 PM Rich Bowen <[email protected]> wrote:
> The PHP docs — https://www.php.net/manual/en/install.unix.apache2.php > specifically — says to use PHP-FPM and mod_proxy_fcgi > > I know because I’m the one that made that change to the docs after > discussing it with various people on both the PHP project and this one. If > that is *not* what we prefer that those docs say, it would be good to know, > and I can attempt to update those docs accordingly. > > > > On Nov 5, 2026, at 11:29 AM, Eric Covener <[email protected]> wrote: > > > >> With mod_fcgid the defacto module for interfacing Apache to PHP, > > > > Specifically on Windows? It's not the defacto interface elsewhere. > > > > On Tue, Nov 3, 2026 at 9:33 AM Peter Kitson <[email protected]> wrote: > >> > >> The Apache + PHP combination is still an enormous part of the internet, > with some 70% of websites reportedly using PHP. > >> > >> With mod_fcgid the defacto module for interfacing Apache to PHP, it > would make sense to me that it should be maintained as part of the standard > development framework, alongside the range of other modules. > >> > >> Jamal has stepped up to the task, and is willing to support this > integration effort, so although I have no real influence per se, I fully > support his endeavours. > >> > >> Regards > >> > >> Pete > >> > >> On 2026/11/03 13:26:08 Joe Orton via dev wrote: > >>> On Tue, Nov 03, 2026 at 12:38:26PM -0000, Steffen Land via dev wrote: > >>>> I think there is enough interest. > >>>> > >>>> Why not release the trunk version ? > >>>> That is asked here a few times with no response. > >>>> When released the interest should grow. > >>> > >>> You can release the trunk version as a new release any time you want > >>> with majority approval from PMC members, that is exactly what being on > >>> the PMC gives you power to do. > >>> > >>>> There are more modules in httpd with no activity for several years. > >>>> Are they kind of death too ? > >>> > >>> It would be better to explicitly declare mod_ftp EOL/unsupported as > >>> well, yes. > >>> > >>> Regards, Joe > >>> > > > > > > > > -- > > Eric Covener > > [email protected] > > The FPM integration is definitely preferable for most deployments, whereas mod_fcgid caters to older installations from mostly the pre-FPM prevalence. You'll also find numerous mod_php deployments because the server administrator didn't look into changing the default mpm, or didn't have time or interest in migrating. Advising against that approach in the php docs is IMO still the best course of action. I'm +1 on supporting older mod_fcgid installations, with the caveat that the user base is mostly either adverse to change, or their legacy application doesn't function under php-fpm for some reason. Fixing egregious bugs is one thing, but I can't see the branch getting much revamping, or updated directives. It's likely to sit in the httpd repo in its current state, or close to it.
