What you can also grasp from the terminal cast above, is that it is now possible to hand over all argument for the setup process as environment variables.

Here is the complete list of default environment variables:

TYPO3_INSTALL_DB_USER
TYPO3_INSTALL_DB_PASSWORD
TYPO3_INSTALL_DB_HOST
TYPO3_INSTALL_DB_PORT
TYPO3_INSTALL_DB_UNIX_SOCKET
TYPO3_INSTALL_DB_USE_EXISTING
TYPO3_INSTALL_DB_DBNAME
TYPO3_INSTALL_ADMIN_USER
TYPO3_INSTALL_ADMIN_PASSWORD
TYPO3_INSTALL_SITE_NAME
TYPO3_INSTALL_SITE_SETUP_TYPE

Just like in previous versions, if you use the --no-interaction flag, only required arguments need to be set. For all optional arguments the default values will be used then.

Last but not least, the whole setup process is now defined in a Yaml file. This means adding new arguments or even completely new steps is a matter of changing configuration.

Overriding the default configuration file is possible by providing the path to your own file with the TYPO3_INSTALL_SETUP_STEPS environment variable. In this file you can decide to either import the default configuration and amend it to fit your needs (e.g. using different environment variables names or even hard code know values), or create a completely customized setup workflow, or even run different setup steps in different scenarios.

We are very much looking forward to what you are going to build with this feature.

Deprecations

The CommandDispatcher::createFromComposerRun() API changed, so that the first Composer event argument is obsolete. Passing it anyway will continue to work, but is deprecated.

Further changes

The full change log can be examined on Github The extension can be found at the TER release page.