[TYPO3-dev] Deploy localconf.php from test to live system
Zachary Davis, Cast Iron Coding LLC
zach at castironcoding.com
Wed Oct 27 17:50:43 CEST 2010
We use Git as well, and this is the approach we take. We track
localconf.php in Git and each environment has a file called
localconf_env.php. We also have a typoscript constants file
(constants_env.txt) that's not tracked in Git. This file contains the
domain name constant, which changes between dev, staging, and
production, as well as other constants which sometimes change, such as
We've been exploring better deployment strategies, but it's a challenge
with TYPO3. One thing we've been considering is implementing a method
for automatically running the database analyzer after deployment, to
deal with new extensions that require new DB tables and fields.
On 10/27/10 7:58 AM, Sebastian Fischer wrote:
>> Solution A:
>> Using git for the rollout, also including localconf.php in git.
>> All system specific settings are in ext_localconf.php of a dedicated
>> configuration extension. This extension overrides the settings of
>> localconf.php and is not deployed with git (via gitignore).
>> Drawback: $TYPO3_CONF_VARS['EXT']['extList'] cannot be covered by this
>> scenario and needs manual action.
More information about the TYPO3-dev