[TYPO3-dev] splitting localconf

[Ernesto Baschny [cron IT]]

Steffen Kamper wrote: on 30.09.2008 10:54:

>> About the terminology, I get your point, but the distinction we usually
>> make is this:
>>
>> 1) machine specific configuration (paths, im-settings), which can be
>> shared along "all" TYPO3 installations on a single machine.
>>
>> 2) site specific, but machine dependant specific settings (db-settings,
>> maybe development settings, i.e. devMask, displayErrors, etc).
>>
>> 3) site specific configuration (which influence the workings of your
>> specific site, no matter on which host it is running.
>>
>> And we set it up on those files:
>>
>> /var/www/shared/localconf.php = 1)
>> typo3conf/localconf.local.php = 2)
>> typo3conf/localconf.php = 3), which includes 1) and 2)
>>
>> We maintain 3) in CVS, to keep it in sync between different environments
>> (this file will also be updated by the install tool and ext manager. We
>> manually move stuff to localconf.local.php when required.
>>
>> Cheers,
>> Ernesto
> 
> thx for sharing your concept.
> The only missing thing is the update from installer or EM so you have to
> copy that stuff manually. Would be nice if there are categories so you
> can specify where to store which settings match to the category :-)

Indeed, could be a good idea.

Cheers,
Ernesto