“how do I _____ on my local machine?”
Pre-requisites to installation:
- Ensure that
docroot/sites/default/settings/local.settings.php
exists by executingblt setup:drupal:settings
. - Verify that correct local database credentials are set in
local.settings.php
. - Ensure that project dependencies have already been built via
blt source:build
To re-install Drupal, execute: blt drupal:install
. Note that this will drop the existing database tables and install Drupal from scratch!
Please dependency management for all information on managing core and contributed packages for your project.
Please see Deploy for a detailed description of how to deploy to Acquia Cloud.
Please see testing.md for information on running tests.
To execute PHP codesniffer and PHP lint against the project codebase, run:
blt validate:all
Please see Frontend for information about compiling front end assets and executing front and build processes.
The project is configured to update the local environment with a local drush alias and a remote alias as defined in blt/blt.yml
or blt/local.yml
. Given that these aliases match, those in drush/sites/
, you can update the site with BLT. Please see drush/README.md for details on how to create these aliases.
This all in one command will make sure your local is in sync with the remote site.
blt drupal:sync
This will sync your site and execute all necessary updates afterwards (cache clears, database updates, config imports).
By default, BLT will not sync your public and private files directories. However, you may set sync.files
to true
in your blt.yml
file to perform a file sync during sync:refresh
tasks by default
within your project.
If you are using multisite, you may refresh every single multisite on your local machine by running:
blt drupal:sync:all-sites
blt drupal:sync:db
This will copy and database (and files if sync.files is set to true) but will not execute any updates afterwards.
blt drupal:update
This will execute various update commands (cache clears, db updates, config imports) to bring the local database in light with your codebase (i.e., exported config).