Re: [RFC] Release Process
| From: | Reindl Harald | Date: | Mon, 03 Jan 2011 02:33:15 +0000 |
| Subject: | Re: [RFC] Release Process | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-51200@lists.php.net to get a copy of this message | ||
Am 03.01.2011 02:19, schrieb Enrico Weigelt:
> In essence you say here, that I should diff the production config
> example from one version to another to find out what changed
> and adapt my config, on each update.
Hm thats your job as sysadmin
> Adds about 15mins extra work
What is your job
> per system and update just for that.
per system?
are you riding totally differnet or random configurations
on many servers?
> Why aren't the production settings the built-in defaults ?
because on development-machines warnings should jump
over your screen before you put a broken application
on a production server
on the other side NEVER EVER any server-software has to go online
withe default settings becuase lazy admins they are not
knowing what they do!
PRODUCTION:
error_reporting = E_ALL | E_STRICT
display_errors = 0
log_errors = 1
DEVELOPMENT:
error_reporting = E_ALL | E_STRICT
display_errors = 1
log_errors = 1
And yes with this settings for 500 domains we having some warnings
every month because applications which are spitting in the log
are fixed or killed because they are not production ready
This way update from 4.0 -> 5.0 -> 5.3 for some servers with
henrets of domains where painless - so what will you tell us
expecting you are not knowing what your configuration does?
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc