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 ...
<FilesMatch \.php$>
SetHandler application/x-httpd-php
</FilesMatch>
AddType text/html .php
Etc,
...typically in the file named php.conf, matter if you do not have mod_php
loaded and are only using PHP-FPM?
What PHP related setting would you possibly put in php.conf if you are
only using PHP-FPM?
In other words, by using PHP-FPM, and using ProxyPassMatch, none of those
things are used. Right?
Except "DirectoryIndex"
Comment: It seems the default/uncommented placement of "DirectoryIndex
index.php" in php.conf would undesirably/unexpectedly replace
"DirectoryIndex index.html index.php etc." in the main body of your
httpd.conf file. If you "Include" conf.d late in your httpd.conf file.
Thanks
On 11/13/15 12:03 PM, "Rich Bowen" <rbowen@xxxxxxxxxxx> wrote:
>-----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 our attention to this is the "DirectoryIndex index.php"
>> line in php.conf and was it conflicting with our "DiretcoryIndex"
>> line in httpd.conf.
>
>
>So ... possibly several different misunderstandings going on here.
>
>First of all, "php.conf" is just an arbitrary file name. httpd doesn't
>care what you name your configuration files, whether it's php.conf,
>foo.bar.conf, or mylittlepony.conf. (And even the .conf is arbitrary.)
>If a file is Include'ed, then it's used.
>
>So if you have
>
>Include *.conf
>
>Then any file named anything.conf is loaded and "used".
>
>Contrariwise, if you have
>
>Include conf/*
>
>then ANY file in that directory is included and used in your
>configuration.
>
>So, yeah, if you have a file named php.conf (or boogity.conf) and
>you've Include'ed it, then it's "used".
>
>As to whether you should rename/delete/comment the configuration file,
>it depends entirely on what's in it, and whether you want that
>configuration to be active. If what's in it is directives that enable
>mod_php, then you are probably safe removing the file, in your
>particular situation, where you're using php-fpm
>
>On the other hand, if you're still using mod_php for something, then
>you might still need that file, or, at least, the directives that are
>contained in it.
>
>Is that clearer?
>
>- --Rich
>
>
>
>
>
>
>
>>
>> Thanks
>>
>> On 11/13/15 11:39 AM, "Rich Bowen" <rbowen@xxxxxxxxxxx> wrote:
>>
>>
>>
>> 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
>>
>>
>>
>>
>>>
>>> ---------------------------------------------------------------------
>>>
>>>
>To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>>> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>>>
>>
>>
>> ---------------------------------------------------------------------
>>
>>
>To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>>
>
>- --
>Rich Bowen - rbowen@xxxxxxxxxxx - @rbowen
>http://apachecon.com/ - @apachecon
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v2
>
>iEYEARECAAYFAlZGF+gACgkQXP03+sx4yJODqACeJzKiSoqgprcFtQnH25S8l4Z3
>slMAoIr7Zzm8jAh5HidDGg+4AL7SBUdT
>=El+s
>-----END PGP SIGNATURE-----
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|