By default, websites running the current Drupal version use the sync configuration directory in your files directory. For example, docroot/sites/default/files. For more information, see Understanding files.
Acquia recommends you to store the configuration in a directory above the docroot in your repository.
Required config/default folder
For websites running the current Drupal version, Cloud Platform requires you to define a default location for the configuration directory where you store Drupal configuration information in your code repository. Typically, this directory is located at:
config/[sitename]
Here, config is a directory at the same level of your docroot directory. You must create the directory as it does not exist in the repository by default. If you do not create the config directory, Cloud Platform displays the following error message:
The directory docroot/../config/default does not exist.
You cannot run update.php until you create the config directory. Also, you cannot commit empty directories in Git.
In the new directory, you must also add the .gitkeep text file before you can commit the directory to your repository. After creating the directory, you have the following file structure at the docroot level:
/docroot/
config/default/
In the settings.php file for your application, define the following config path:
To understand the process of pushing the configuration, assume that you want to build or update an application named example that runs the current Drupal version in the Development environment in Cloud Platform. Acquia recommends you to use Acquia Cloud IDE or a local development environment as Cloud Platform is read-only.
To export and push the configuration:
Export the configuration with the following command:
drush config-export --uri=default
The system displays the following message:
[notice] The active configuration is identical to the configuration in the export directory (../config/default).
Review the changes with the following command:
git show
Verify the changes before pushing them.
If you are satisfied with the changes, push them with the following commands:
By default, websites running the current Drupal version use the sync configuration directory in your files directory. For example, docroot/sites/default/files. For more information, see Understanding files.
Acquia recommends you to store the configuration in a directory above the docroot in your repository.
Required config/default folder
For websites running the current Drupal version, Cloud Platform requires you to define a default location for the configuration directory where you store Drupal configuration information in your code repository. Typically, this directory is located at:
config/[sitename]
Here, config is a directory at the same level of your docroot directory. You must create the directory as it does not exist in the repository by default. If you do not create the config directory, Cloud Platform displays the following error message:
The directory docroot/../config/default does not exist.
You cannot run update.php until you create the config directory. Also, you cannot commit empty directories in Git.
In the new directory, you must also add the .gitkeep text file before you can commit the directory to your repository. After creating the directory, you have the following file structure at the docroot level:
/docroot/
config/default/
In the settings.php file for your application, define the following config path:
To understand the process of pushing the configuration, assume that you want to build or update an application named example that runs the current Drupal version in the Development environment in Cloud Platform. Acquia recommends you to use Acquia Cloud IDE or a local development environment as Cloud Platform is read-only.
To export and push the configuration:
Export the configuration with the following command:
drush config-export --uri=default
The system displays the following message:
[notice] The active configuration is identical to the configuration in the export directory (../config/default).
Review the changes with the following command:
git show
Verify the changes before pushing them.
If you are satisfied with the changes, push them with the following commands: