Problem/Motivation
In #3587140: Make maintenance easier: update ddev-drupal-contrib, phpstan, we added some DDEV tooling to make it easier to set up Scanner-Fixer API for contributing.
In a similar issue for another module, @boromino and @mparker17 came up with a script to further simplify setting up the module for development: a custom ddev reset-test-env command to install dependencies, re-installs Drupal and the module, and display a link that contributors can use to log into the test site.
This seems like a useful addition to Scanner-Fixer API, so lets port that custom command to this module.
Proposed resolution
Add a .ddev/commands/host/reset-test-env file that looks like...
#!/bin/bash
ddev poser
ddev exec "cd web/core && yarn install"
ddev symlink-project
ddev drush -y site:install standard
ddev drush -y pm:install scanner_fixer_api_test
ddev drush -y uli
Once this issue is merged, update the documentation accordingly.
Remaining tasks
Merge request- merge request !7 created by @mparker17 in #2Community/Maintainer review- skipped by @mparker17 in #5Commit 3.0.x- done by @mparker17 in #6Commit 2.0.x- done by @mparker17 in #7Update docs- done by @mparker17 in #8- Release 3.0.x
- Release 2.0.x
User interface changes
None.
API changes
None.
Data model changes
None.
Issue fork scanner_fixer_api-3588285
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
mparker17Created merge request !7. Let's see what testbot thinks.
Comment #4
mparker17To manually test, clone a new copy of scanner_fixer_api, and set it up like...
... you should get a working dev environment.
Comment #5
mparker17Skipping community/maintainer review because it was authored and tested by a maintainer. Merging; after, I will cherry-pick to 2.0.x.
Comment #8
mparker17Merged and cherry-picked to the 2.0.x branch. I also updated the documentation. I will update this issue when these changes make it into a release.