At 04:39 PM 1/3/2002 -0500, Jon Parise wrote:
On Thu, Jan 03, 2002 at 04:26:38PM -0500, J Smith wrote:
Just a little annoyance I guess. Nothing to get in knots over. But in the
end, I would prefer separate php.ini files, maybe something like
php-cli.ini for the default CLI file and and php.ini for the Apache/web
server module default. If php-cli.ini doesn't exist, the CLI can always
fall back on php.ini, which would be the default in any case.
I agree that it's sometimes necessary to have different
configuration files, but I don't consider it a necessity.
It should still be possible to build a separate CGI executable
with a different php.ini path for those sites that require it.
I don't think it's necessary to alter the build process to make
that the rule, though.
Your suggestion of a separate php-cli.ini has merit, but who will
the php binary know when it's being used for CLI purposes and not
as a CGI?
We could have the CLI version check for a PHP_INI environment variable and if it exists use that instead. Wrapping cli on your own with the right environment variable should be no problem for anyone.
Andi