Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Rose, John B
Thanks Rich, Daniel, Chris for taking the time to reply. On 11/13/15 4:01 PM, "Rich Bowen" wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > > > >On 11/13/2015 02:53 PM, Rose, John B wrote: >> do the settings such as ... >> >> SetHandler application/x-httpd-php >> >> >> >> AddType t

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Rich Bowen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/13/2015 02:53 PM, Rose, John B wrote: > do the settings such as ... > > SetHandler application/x-httpd-php > > > > AddType text/html .php > > Etc, > > ...typically in the file named php.conf, matter if you do not have > mod_php loaded

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Christopher Schultz
John, On 11/13/15 2:53 PM, Rose, John B wrote: > Let me rephrase my question. > > I understand the .conf file names can be anything. > > I may should have asked it this way, do the settings such as ... > > > SetHandler application/x-httpd-php > > > > > AddType text/html .php > > Etc,

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Daniel
Yes, you don't need the SetHandler any more the same way you used it with mod_php. A handler tells apache how to "react" with certain types of files. If you migrated to php-fpm you would either use proxypass/rewriterule with P or you use a handler like: # Unix sockets require 2.4.7 or la

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Rose, John B
Let me rephrase my question. I understand the .conf file names can be anything. I may should have asked it this way, do the settings such as ... SetHandler application/x-httpd-php AddType text/html .php Etc, ...typically in the file named php.conf, matter if you do not have mod_php l

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Rich Bowen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/13/2015 11:46 AM, Rose, John B wrote: > mod_php is not enabled. > > So you are saying if mod_php is NOT enabled and we are using > PHP-FPM, then php.conf is not used? > > Or we should rename it? Comment all the lines in it out? > > What drew

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Daniel
Files do not represent anything in apache, file names even less. All configuration files are created equal. It does not matter which of the configuration files you put the directive in. What does matter is whether you put it in the appropriate context. Put directives somewhere that makes sense to

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Rose, John B
mod_php is not enabled. So you are saying if mod_php is NOT enabled and we are using PHP-FPM, then php.conf is not used? Or we should rename it? Comment all the lines in it out? What drew our attention to this is the "DirectoryIndex index.php" line in php.conf and was it conflicting with our "Di

Re: [users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Rich Bowen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/13/2015 11:24 AM, Rose, John B wrote: > > If we are using PHP-FPM with Apache. Is there any reason to have > conf.d/php.conf? > If you're asking if you need mod_php enabled, then, no, you don't need that when you're using php-fpm - --

[users@httpd] php.conf and PHP-FPM

2015-11-13 Thread Rose, John B
If we are using PHP-FPM with Apache. Is there any reason to have conf.d/php.conf?