-
run
composer install
-
create settings.local.php file in web/sites/default and add your database connection; don't forget to add your local development hostname to 'trusted_host_patterns'
-
import database and sync files from STAG (or unzip files archive if you have one) in web/sites/default/files
-
perform drush 'flow' in case your database state is older than the codebase (yml config):
drush updb
drush cim
drush cr
-
build FE: Node >= 16 is required
⚠️ - run
yarn
to install all FE dependencies - run
yarn build-dev
to build the FE for development - run
yarn build-watch
to watch for CSS/JS changes (during development)
- run
- Lando needs to be installed on the machine
- copy example-[x86-64/aarch64].lando.yml (2 versions for different architectures available) and name it .lando.yml in project root
- copy lando-example.settings.local.php in web/sites/default and rename to settings.local.php
lando start
lando composer install
lando db-import database.sql
To update a contributed module run:
composer update drupal/module_name
To update Drupal core and all its dependencies run:
composer update drupal/core-recommended -W
A lot of times a core update will come with update hooks. After composer is done you should always run:
drush updb
If the previous command shows and performs update hooks, make sure to export the changes and commit them to the repository:
drush cex -y
A lot of the content was migrated from Drupal 7. To execute a migration (if you've set up a connection to the D7 database) run:
drush mim migration_id
To rollback a migration run:
drush mr migration_id
After executing a migration Drupal will create a table in the database which represents a migration mapping, e.g. if old node IDs are not kept, you can use the mapping to see which target ID corresponds to which source ID after the migration. The table will be named something like: migrate_map_migration_id.