The Probo Drupal plugin provides an easy way to set Drupal site configuration options in a Probo Build and quickly integrate a Drupal website’s repository. To use the Probo Drupal plugin you must declare plugin: Drupal
in your .probo.yaml
file. The Drupal plugin’s parameters can automate some steps specific to Drupal such as reverting features, running database updates, clearing caches, or performing other build configuration steps.
The Probo Drupal plugin inherits all Probo LAMP plugin configuration options. This allows additional Probo Build steps in your .probo.yaml
file to layer LAMP configuration options and commands on top of the Drupal site specific configuration.
See the Probo Drupal Plugin Examples section below for YAML config examples specific to Drupal.
Directory Configuration
-
configSyncDirectory
{string}Specify the location of the Drupal 8 configuration synchronization directory relative to a Drupal 8 site’s root directory. Defaults to
sites/default/files/config_HASH/sync
, whereHASH
is a random string generated and used for the$settings['hash_salt']
value in the settings.php file.Example
-
makeFile
{string}The name of the Drush make file to run to generate the install directory.
Example
-
makeForceComplete
{boolean}Whether to use the
--force-complete
option fordrush make
. Defaults totrue
.Example
-
makeArgs
{array}A set of parameters to concatenate onto the
drush make
command. -
profileName
{string}The profile name used in creating a symlink to this directory if a Drush make file is specified with the
makeFile
option. Used to select the profile to install if therunInstall
option is selected. -
runInstall
{boolean}If set, run
drush site-install
to perform a fresh install of the site using theprofileName
as the install profile and allowing theinstallArgs
option to configure the install. -
installArgs
{string}A set of parameters to concatenate onto the
drush site-install
command if therunInstall
option is set. Defaults to ‘’. -
siteFolder
{string}Specifies the site folder to use for this build (the folder within the Drupal
sites
folder). Defaults todefault
.Example
-
subDirectory
{string}The path to your docroot if it is a subdirectory of your git repository.
Database Configuration
-
database
{string}The file name of the database to import if specified. Note that this database must be added to the assets array separately.
Example
-
databaseGzipped
{boolean}Whether the database was sent gzipped and whether it should therefore be gunzipped before importing.
Example
-
databaseBzipped
{boolean}Whether the database was sent bzipped and whether it should therefore be bunzipped before importing.
Example
Settings.php Options
-
settingsRequireFile
{string}A file to require at the end of settings.php. This option helps you to avoid checking settings.php into your repository.
Example
-
settingsAppend
{string}Specify a snippet, such as a variable, to append to the end of the settings.php file.
Example
Additional Options
-
drupalVersion
{integer}Specifies which version of Drupal you are using so that the appropriate commands can be run. For example, if you specify “7” the
clearCaches
option will rundrush cc all
. Drupal 8 and higher will rundrush cr
. Defaults to 8. Accepts the integer values 6 - 9.Example
-
databaseUpdates
{boolean}Determines whether to run
drush updb
after the build is finished.Example
-
clearCaches
{boolean}Whether to clear all caches using
drush cc all
after the build is finished. Pair with thedrupalVersion
option to ensure the proper command is run for your version of Drupal. Defaults to true.Example
-
revertFeatures
{boolean}Whether to revert features using
drush fra
after the build is finished. To use this option, your site must have the Features module installed. This is ignored on Drupal 8 installs and higher.Example
Probo Drupal Plugin Examples
Using the Drupal
plugin
Using the Settings Options
Setting LAMPApp
PHP Configuration Options on a Drupal Installation