Re: Proposal: allow for includes in php.ini
| From: | Michael Shadle | Date: | Wed, 23 Dec 2009 21:25:42 +0000 |
| Subject: | Re: Proposal: allow for includes in php.ini | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-46515@lists.php.net to get a copy of this message | ||
On Wed, Dec 23, 2009 at 10:47 AM, Pierre Joye <pierre.php@gmail.com> wrote:
> Please tell me one benefit except "we support include"? I don't see
> any. The extra files are still there, they will be loaded too, etc.
Instead of a -single location- being defined at compile time or
execution of PHP time, this allows it N number of include directories.
It opens up multiple usage models. for example, cpanel puts a
per-account apache configuration inside of /home/$account/ - it just
seems like a more flexible solution instead of static configure
location. and environment variable override for a web-driven thing
like php-cgi or php fpm has to be done before it is launched...