What are some troubleshooting methods that utilize this config to “helps to determine when the issue is php and when the issue is Apache.”
Thanks From: Daniel <dferra...@gmail.com> Reply-To: "users@httpd.apache.org" <users@httpd.apache.org> Date: Friday, April 7, 2017 at 9:18 AM To: "<users@httpd.apache.org>" <users@httpd.apache.org> Subject: Re: [users@httpd] What is preferred PHP interface? Unless you recompile mod_php and all its extensions to be thread-safety, the most manegeable and performant solution will always be: Apache w/ mpm_event + mox_proxy_fcgi -> php-fpm Besides php-fpm is a very complete daemon/service to serve php, it allows for different pools with pretty different configurations/users/permissions/paths, etc. and to have a separate service for php content helps much. For example, an added benefit from this setup is, for the not too experienced, it helps to determine when the issue is php and when the issue is Apache. I see lots of folks in stackoverflow or asking for help in the #httpd channel at Freenode who confuse their problems as Apache being the source of them instead of PHP scripts or the php configuration itself. 2017-04-07 2:45 GMT+02:00 William A Rowe Jr <wr...@rowe-clan.net<mailto:wr...@rowe-clan.net>>: There is little activity on mod_fcgid because it works. There has been talk of tagging 2.3.10 at some point for very minor fixes. Mod_proxy_fcgi is a viable alternative, and offers the ability to load balance, but managing the process pool of available fcgi workers is offloaded from httpd and becomes a distinct ops responsibility. It too has changed little since 2013. -- Daniel Ferradal IT Specialist email dferradal at gmail.com<http://gmail.com> linkedin es.linkedin.com/in/danielferradal<http://es.linkedin.com/in/danielferradal>
