| 39 | | Profile cloning is configured at a very early stage of the compilation process. As a result, it doesn't have access to the variables defined by the standard configuration process but needs to access directly some of specific site templates. If you don't use the standard names for these profiles, you should define the following variables: |
| 40 | | * `SITE_DATABASES`: name of the template defining variables `DB_MACHINES` and `DB_IP`. Default: `site/databases`. |
| 41 | | * `SITE_GLOBAL_VARIABLES`: name of the template defining global variables for the site. Default: `site/global_variables`. |
| 42 | | * `SITE_FUNCTIONS`: name of the template defining site specific functions. Default: `site/functions`; |
| 43 | | * `SITE_CONFIG`: name of the template defining the base site configuration. Default: `site/config`. |
| | 39 | Profile cloning is configured at a very early stage of the compilation process. As a result, it doesn't have access to the variables defined by the standard configuration process but needs to access directly some of specific site templates. If you don't use the standard names for these profiles, you should define the following variables (that are used by the standard configuration process and have the same defaults): |
| | 40 | * `SITE_DB_TEMPLATE`: name of the template defining variables `DB_MACHINES` and `DB_IP`. Default: `site/databases`. |
| | 41 | * `SITE_GLOBAL_VARS_TEMPLATE`: name of the template defining global variables for the site. Default: `site/global_variables`. |
| | 42 | * `SITE_FUNCTIONS_TEMPLATE`: name of the template defining site specific functions. Default: `site/functions`; |
| | 43 | * `SITE_CONFIG_TEMPLATE`: name of the template defining the base site configuration. Default: `site/config`. |