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

[Stefan Geith]

Hi Devs,

Am 31.10.2010 08:49, schrieb Christian Opitz:
> i'm very interested in a solution for that problem too. In other
> applications like Zend Framework I've seen the possibility to define an
> environment and environment based settings. With that approach it's even
> possible to define your environment in the htaccess:
>
> #.htaccess:
> SetEnv TYPO3_ENV development
>
> //index.php
> defined('TYPO3_ENV')
> || define('TYPO3_ENV', (getenv('TYPO3_ENV') ? getenv('TYPO3_ENV') :
> 'production'));

I did that directly in localconf.php:
   defined('TYPO3_ENV') || define('TYPO3_ENV', (getenv('TYPO3_ENV') ? 
getenv('TYPO3_ENV') : 'UNCONFIGURED !!!!!'));
   $TYPO3_CONF_VARS['SYS']['TYPO3_ENV'] = TYPO3_ENV;
   $TYPO3_CONF_VARS['SYS']['sitename'] = 'MyWebSite ('.TYPO3_ENV.')';

And in .htaccess, I have set
   SetEnv TYPO3_ENV dev
oder
   SetEnv TYPO3_ENV preview
etc.

BUT:
this does not work with sheduler tasks, because .htaccess is not used 
with CLI...
Any idea, where I could add this definition more easily than
directly in the crontab ?

/Stefan




>
> Cheers,
> Christian
>
> Am 28.10.2010 10:33, schrieb Stefan Geith:
>> Am 28.10.2010 10:19, schrieb Steffen Müller:
>>> Summing up our goal is:
>>> We are looking for a place to configure stuff _after_ localconf.php and
>>> _before_ extensions get loaded.
>>> The goal is to have a (foolproof) control of these setting:
>>> $TYPO3_CONF_VARS['EXT']['extConf']
>>> $TYPO3_CONF_VARS['EXT']['extList']
>>> $TYPO3_CONF_VARS['EXT']['extList_FE']
>>>
>>> Looking at config_default.php, it does not exist. Nicos patch seems to
>>> be a solution. IMHO it seems others might also find it useful,
>>
>> +1
>>
>> Waiting for this quite some time ;)
>>
>> /Stefan
>>
>
> _______________________________________________
> TYPO3-dev mailing list
> TYPO3-dev at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-dev