- Issue created by @joelpittet
- 🇨🇦Canada joelpittet Vancouver
Need a tester to see if it will work before committing.
I've been maintaining my contrib projects using https://github.com/ddev/ddev-drupal-contrib for some time now, and have just been leaving the .ddev folder uncommitted.
But now that DDEV has become the gold standard for Drupal local development, I feel it is now safe to commit the .ddev folder to the project (as recommended by ddev-drupal-contrib) and then document in the README.md how to setup a local environment for contribution/maintenance.
Optional. Commit the changes in the .ddev folder after this plugin installs. This saves other users from having to install this integration.
Other projects where .ddev has been committed (by Moshe - Maintainer of DDEV Drupal Contrib).
https://git.drupalcode.org/project/domain_perm/-/tree/2.0.x?ref_type=heads
drush/drush to dev dependencies of the composer.json for standard cli tooling access. Note this module currently doesn't have any custom Drush commands, but it helps to have a fully functional DDEV local environment including drush, and it seems this is currently the only way.Active
4.3
Miscellaneous
Need a tester to see if it will work before committing.