If you plan to use a HMR theme via the lando proxy, you need to trust your Lando SSL certificates.
lando start
lando drush uli
lando npm <command>
lando theme install
lando theme run dev
Clear Drupal cache to start using Vite HMR.
lando theme run build
proxy:
node:
- node.<< LANDO APP NAME >>.lndo.site:3000
Create /.lando.local.yml
file for local development. See docs.
Get database credentials:
lando info -s database --path "0.creds" --format table
Get database host and port:
lando info -s database --path "0.external_connection" --format table
lando info -s mailhog --path "0.urls"
When installing the given composer.json
some tasks are taken care of:
- Drupal will be installed in the
web
directory. - Autoloader is implemented to use the generated composer autoloader in
vendor/autoload.php
, instead of the one provided by Drupal (web/vendor/autoload.php
). - Modules (packages of type
drupal-module
) will be placed inweb/modules/contrib/
- Themes (packages of type
drupal-theme
) will be placed inweb/themes/contrib/
- Profiles (packages of type
drupal-profile
) will be placed inweb/profiles/contrib/
- Creates the
web/sites/default/files
directory. - Latest version of drush is installed locally for use at
vendor/bin/drush
.
No.
If you need to apply patches (depending on the project being modified, a pull request is often a better solution), you can do so with the composer-patches plugin.
To add a patch to drupal module foobar insert the patches section in the extra section of composer.json:
"extra": {
"patches": {
"drupal/foobar": {
"Patch description": "URL to patch"
}
}
}