Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
To: users@httpd.apache.org
References: <D26B7906.61E15%jbrose@utk.edu> <5646124A.3010901@rcbowen.com>
 <D26B7CCC.61E1B%jbrose@utk.edu>
From: Rich Bowen <rbowen@rcbowen.com>
Message-ID: <564617EF.8010207@rcbowen.com>
Date: Fri, 13 Nov 2015 12:03:43 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <D26B7CCC.61E1B%jbrose@utk.edu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [users@httpd] php.conf and PHP-FPM

-----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@rcbowen.com> 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@httpd.apache.org
>> For additional commands, e-mail: users-help@httpd.apache.org
>> 
> 
> 
> ---------------------------------------------------------------------
>
> 
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
> 

- -- 
Rich Bowen - rbowen@rcbowen.com - @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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org