[TYPO3-dev] Deploy localconf.php from test to live system

[Nico de Haen]

Everything that is configured by the Install tool is no problem. The
install tool can be uninstalled and all TYPO3_CONF_VARS required can be
set by an include before the auto generated stuff. Only the
$TYPO3_CONF_VARS['EXT'] variables are are a bit difficult: we would have
to manually modify these after installing an extension or after
modifiying an extension setting, since we have several extensions that
we don't want to have installed in the productive system.

It would be useful to have a hook or a defined filename that is included
after including the localconf.php if it exists...

Nico




Am 27.10.2010 21:09, schrieb Zachary Davis, Cast Iron Coding LLC:
> Not much of a drawback, though, if the only goal is to break out the DB
> connection info for each environment, which is all we're trying to do.
> We've never had a problem with the include being over-written, since
> it's included near the top of the file.
> 
> In any case, it's certainly not ideal. But, for large projects, we have
> to have ways to track the source effectively and to deploy across
> multiple environments, so we do what we can. I'd love to see a future
> release of TYPO3 that made it easier to break out environment-specific
> settings, but the system isn't quite there yet.
> 
> Zach
> 
> 
> On 10/27/10 9:17 AM, Nico de Haen wrote:
>> Hi,
>>
>> all these approaches have the drawback, that you can't include anything
>> after the last line of the auto generated localconf.php. It will be
>> overriden each time the ExtensionManager is touched...
>>
>> Nico
>>