Re: set the PHP_INI_ENTRY_* values the same as for php.ini-production
On 03/14/2012 10:27 AM, Rasmus Lerdorf wrote:
The biggest problem with the concept of virgin PHP settings being geared
for production is that by definition that isn't very developer friendly.
Keeping the learning curve shallow has always been a goal for PHP which
is why things like display_errors exist. A new developer may not have
any idea where to look for PHP errors and might give up when all he gets
is a blank page.
The assumption is that by the time you are ready to put something into
production you have spent a little bit of time with PHP and you likely
have stumbled across the suggested production php.ini which is then
trivial to apply.
In that case, perhaps the STD_PHP_INI_* values should match those
in php.ini-development?
Chris
--
Email: [email protected]
Tel: +1 650 506 8630
Blog: http://blogs.oracle.com/opal/
Thread (10 messages)