[TYPO3-core] New LocalConfiguration.php (2) - Some Thougts

Christian Kuhn lolli at schwarzbu.ch
Wed Aug 1 07:31:43 CEST 2012


On 07/31/2012 04:01 PM, Stefan Geith wrote:
> When looking at my newly converted LocalConfiguration.php,
> I can see, that there are still (as in localconf.php) mixed
> server-dependent and site-dependent settings.
> Maybe it would make sense to spit LocalConfiguration.php
> to two files:
> (1) One containing server-dependent information like
>      e.g. DB-Connection,
>           filesystem-settings (createGroup etc.)
>           IM-Verisons and Settings
> (2) and the other containing site-dependent information
>      e.g. all ext-settings
>           FE-, SYS-Settings
> This would be useful e.g. when copying form a dev-site
> to the live-site, because site-dependent settings could be untouched
> and you would only have to change the server-dependent localconf.

The core currently has no real support for this. For now, you have to 
live with AdditionalConfiguratation.php to 'overload' your settings 
somehow (eg. with a hostname check, a path check, or an environment 

We discussed this topic on our bootstrap code sprint, but were unable to 
come up with a good concept to handle environments / scope / context.

Furthermore, we still have all hands full with disentangling the 
bootstrap and to make the code flexible enough to come up with a well 
thought concept in the end. From core view, the localconf change for 
example gave us a definition of which code is in it and to do further 
things with it. It enables us to now for example split out scope 
specific segments, this was impossible before. I hope we will see more 
in this area for 6.1, the ground work should be done.


More information about the TYPO3-team-core mailing list