TYPO3 Core

localconf.php is a big flat configuration file. We have a marker to separate "static" part (at the beginning) and dynamically generated/managed (through install tool / EM) at the end.

However in some situations it would be useful to be able to have static configuration at the end too.

Moreover, adding or removing extensions is a pain because it forces us (or the underlying tool) to manipulate a comma-separated list of extension keys. This could be replaced by some clever array instead.

Idea from Steffen Kamper would be to have static methods (or singleton configuration class methods) provided to manipulate the configuration. E.g.,

$GLOBALS['T3_CONFIG']->loadExtension('realurl');
$GLOBALS['T3_CONFIG']->getDatabaseConfiguration()->setUsername('db-username');

Speed and caching should be taken into account to prevent slowing down the whole instantiation process.
(issue imported from #M17972)