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
The following file
/sites/default/settings.php is only executed when no site is found for a domain.
Other key concepts:
- Includes references to various
*.settings.phpfiles (* = files, cron, dev, testing, etc.)
- Settings configuration in this file, as well as the
*.settings.phpfiles are all duplicated in either
- Does not get run on Acquia Cloud Site Factory, as all settings configuration is handled by
/sites/g/settings.php is not allowed to be changed.
- Added via initialization of the
- Invokes pre/post cloud hooks
- Includes site-specific settings file that is not in the code repository, but hosted separately on Acquia Cloud Site Factory
- Immutable. All changes to this file should come via the
acsf-initdrush command. More information about
acsf-initcan be found at Using your own Drupal distribution
- Additional settings should be added via the respective pre/post factory hook settings files
Factory 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 documentation on Triggering code execution.