[TYPO3-dev] Feature Request: Splitting localconf.php into hard

[Joerg Schoppet]

Martin Kutschker Wrote:

> 
> How is the external versioning to be triggered?
> 
> Both the installer and the ext. manager would have to do a checkout/commit 
> regardless of how many parts you split localconf.php into.
>

I don't think about automated versioning out of typo3. This should be done manually.

> But there is relief:
> 
> There is only a single function in TYPO3 that writes to localconf.php:
>   t3lib_install->writeToLocalconf_control()
> 
> The new version of TYPO3 4.0 already writes to a temp file first. Write an 
> XCLASS that does the correct procedure for your version control system.
> 

This sounds interesting. So I would make an extension, in which you can define special files for each array-keys.
e.g.
BE -> localconf.php
ext -> localconf_dynamic.php
and so on

But a major problem still exists.
How can I explain typo3, that it should load all this additional files, defined in my extension?
One solution would be a configuration-setting in localconf.php similar to realurl.
But I see in such a solution a lot of problems. (e.g. if I define, that all the ext-stuff should go to localconf_dynamic.php, then I have the problem, that I have to use an extension before it is loaded by typo3). Do you see my concerns?

Regards
Joerg