Login
< CMS Certified Integrator 14 LTS

System Configuration Files

TYPO3

Show in app

Description

A Composer-based TYPO3 project uses a small set of well-defined PHP files to control the entire system configuration. Integrators need to know which file stores what, who writes to it, and how the files relate to each other — particularly `settings.php` and `additional.php` in `config/system/`, which together populate the global `$GLOBALS['TYPO3_CONF_VARS']` array.

Goals

  • I know the purpose of `config/system/settings.php` as the machine-written file that persists `$GLOBALS['TYPO3_CONF_VARS']`, and that TYPO3 overwrites it whenever settings are changed in the backend.
  • I know the purpose of `config/system/additional.php` as the manually maintained file that can override or extend values from `settings.php`, and that TYPO3 never touches it automatically.
  • I know that `additional.php` is the correct place for environment-specific configuration such as database credentials, and that this file must not be committed to version control.
  • I know that `additional.php` supports PHP control structures such as `if` conditions, which allows switching configuration values — for example database credentials — based on the current Application Context.

Maintainer

Oliver Thiele Web Development Oliver Thiele