Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58932
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F60D511.1050802@lerdorf.com>
References: <CAH-PCH5jJ1ctJy6kZcyMLxSKyJs=+pA8ivB89MEzQtKfJWiHMQ@mail.gmail.com>
	<CAKUjMCW+j=fL4oS1+cQ6QMy1ZGPK-sy=af7gnL2NJq86_yh4Vg@mail.gmail.com>
	<CAH-PCH7WKbvPPU1N0uuFB416Sf_tpG+w++kRgdRgnZRexG=PJw@mail.gmail.com>
	<4F60D511.1050802@lerdorf.com>
Date: Wed, 14 Mar 2012 18:37:59 +0100
Message-ID: <CAH-PCH4yz5fe=qNUTpKR6-ZCGX0d28W2amdp9jnbhXVKnAysZQ@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: RQuadling@gmail.com, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d04170191c1724204bb376f24
Subject: Re: [PHP-DEV] set the PHP_INI_ENTRY_* values the same as for php.ini-production
From: tyra3l@gmail.com (Ferenc Kovacs)

--f46d04170191c1724204bb376f24
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 14, 2012 at 6:27 PM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 03/14/2012 10:09 AM, Ferenc Kovacs wrote:
> > On Mon, Jul 25, 2011 at 12:34 PM, Richard Quadling <rquadling@gmail.com
> >wrote:
> >> Maybe, and this is right of the top of my head, if PHP is installed
> >> for a production environment with no INI file, or if an ini file
> >> doesn't alter any of the core settings (maybe a separation of INI
> >> files for core and extensions?), it could be labelled/considered as a
> >> virgin PHP install. Something which could be marketed / advertised.
> >> Essentially, the PHP Group agree that for a production environment,
> >> these are the settings that are the safest to use. If there are
> >> considerations that need to be made for shared hosters, then maybe
> >> some mechanism to set these appropriately. So, for a user coming to an
> >> ISP and looking at hosting, they can see "We use Virgin PHP Settings"
> >> or something like that and know that they won't be different to a
> >> documented "standard". Add this labelling to the phpinfo() page and it
> >> makes things very very clear what is in play.
> >>
> >> Richard.
> >>
> >> --
> >> Richard Quadling
> >> Twitter : EE : Zend : PHPDoc
> >> @RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea
> >>
> >
> > bump
>
> 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.
>
> -Rasmus
>
>
imo the average developer will have php installed through some wamp stack
or the distribution/package manager of his platform, so he/she will have a
php.ini with some sane defaults.
another idea coming from Philip is to have a php.ini-default which could
match with the hard-coded defaults.
either way, I think it would be really nice to have a php.ini which we
could refer as default in the documentation, and people shouldn't need to
look up the php-src to figure out what are the hard-coded defaults and how
those are different from the production/development values.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--f46d04170191c1724204bb376f24--