It is important to understand the layers of execution of various settings files used on Site Factory sites despite customers not having direct access to modify these files.
For example, let's look at the differences between /sites/default/settings.php and /sites/g/settings.php.
The following file /sites/default/settings.php is only executed when no site is found for a domain.
Other key concepts:
*.settings.php files (* = files, cron, dev, testing, etc.)*.settings.php files are all duplicated in either pre or post cloud hook settings.php filessites/g/settings.php and cloud-hooksThe file /sites/g/settings.php is not allowed to be changed.
Key concepts:
acsf moduleacsf-init drush command. More information about acsf-init can be found at Using your own Drupal distributionFactory hooks are used to perform various website actions that occur during runtime, or to perform code execution after runtime events. More information about using Factory hooks can be found in our Hooks in Site Factory documentation.