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

[Dennis Cheung]

Hi,

If you ask me.
Dynamc configuration should not save into php. All php should be "READ
and EXEC ONLY".  The configuration should save into ini or serialized
file.

But that is not a response to your suggestion.


If you are looking for common default config.
There is another file named "config_default.php" under t3lib.

Just move your HARD setting before require(PATH_typo3conf.'localconf.php')

Dennis


On 3/10/06, Joerg Schoppet <joerg at schoppet.de> wrote:
> Hi list,
>
> this is a feature request concerning the localconf.php file.
> I just want to make a discussion at first, before I'll open a feature request on bugs.typo3.org.
>
> Problem:
> If you work in an enterprise environment, where a lot of people develop on a typo3-instance, you may need to use a version control system like cvs or subversion to track all kind of changes.
> Through the possibility of "INCLUDE_TYPOSCRIPT" you can put the most TS-Code under version control.
> The last (big) problem I see is the localconf.php file. This file is, in my opinion, the most important file (one wrong change and the complete typo3 stopps). The problem with this file is, that each extension install and deinstall and extension-configuration writes in this file, so it is nearly impossible to make a wise external version control.
>
> Explanation:
> After my experience the localconf.php file exists of to main parts, which I will call 'HARD' and 'SOFT':
>
> - HARD
> The 'HARD' part are the most setting from the install tool, these variables don't change very often. After the initial configuration changes are very rarely.
>
> - SOFT
> The 'SOFT' part contains all the extension relevant stuff, which are primary inserted by the Extension Manager.
>
> Suggestion:
> Split the localconf.php file into two different files. Perhaps localconf_primary.php and localconf_dynamic.php. So you also have the possibility to simply copy the complete typo3conf-dir to a new location, delete the localconf_dynamic.php file and slightly modify the localconf_primary.php to have a new system up and running in a very short time.
>
> Alternatives:
> You can save all the 'HARD' part into a separate file and include this file into localconf.php.
> Drawback:
> If you make a change in the install-tool, these changes are written in the localconf.php file and so you always have to check your 'special'-file against to localconf.php file.
>
>
> Hope to see some constructive comments.
>
> Regards
>
> Joerg Schoppet
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
>