Skip to content
Snippets Groups Projects
Commit b3a89e8b authored by danielspeicher's avatar danielspeicher
Browse files

#9

parent 192f1f35
No related branches found
No related tags found
No related merge requests found
Pipeline #33648 passed
......@@ -17,7 +17,7 @@ It currently scans all composer packages with the pattern `lakedrops/*` and coll
## Prepare a LakeDrops plugin for Ahoy
When your comploser plugin should support this Ahoy framework, simply create a file called `.ahoy.l3d.yml` in the root of your plugin with content similar to this:
When your composer plugin should support this Ahoy framework, simply create a file called `.ahoy.l3d.yml` in the root of your plugin with content similar to this:
```yaml
ahoyapi: v2
......
......@@ -11,9 +11,9 @@ This composer plugin prepares your Drupal project for Behat tests.
## Requirements
The plugin works with any composer based Drupal project and can be added to such projects with `composer require lakedrops/behat4drupal`. It's recommended to also use the Docker4Drupal plugin (added with `composer require lakedrops/docker4drupal`) which will provide all the Docker containers for your development environment as well as those for Selenium and Chrome.
The plugin works with any composer based Drupal project and can be added to such projects with `composer require lakedrops/behat4drupal`. It's recommended to also use the [Docker4Drupal plugin](/composer/plugin/d4d) (added with `composer require lakedrops/docker4drupal`) which will provide all the Docker containers for your development environment as well as those for Selenium and Chrome.
If your project is based on either [Drupal 8 Project Template](https://gitlab.lakedrops.com/composer/project/drupal-8) or [Drupal 9 Project Template](https://gitlab.lakedrops.com/composer/project/drupal-9), then everything is already included for you automatically.
If your project is based on either [Drupal 8 Project Template](/composer/project/d8) or [Drupal 9 Project Template](/composer/project/d9), then everything is already included for you automatically.
## Usage
......
......@@ -97,7 +97,7 @@ The following services are available in your browser while the Docker containers
- Node http://front.[PROJECTNAME].docker.localhost:8000
- Varnish http://varnish.[PROJECTNAME].docker.localhost:8000
Note that Solr, Node and Varnish are not enabled by default. See the customization chapter below to learn how you can enable them.
Note that Solr, Node and Varnish are not enabled by default. See the [customization](/composer/plugin/d4d#customization) chapter below to learn how you can enable them.
### PHP Debugging
......@@ -131,7 +131,7 @@ For the configuration of the access, you need to do two things:
#### Configure your Drush alias
In your project root on your host you'll find a `drush` subdirectory with a file called `aliases.drushrc.php` with a `dev` and a `live` alias. THe first one is configured automatically and the second is empty by default. You have to provide the details manually:
In your project root on your host you'll find a `drush` subdirectory with a file called `aliases.drushrc.php` with a `dev` and a `live` alias. The first one is configured automatically and the second is empty by default. You have to provide the details manually:
- **root**: the full path to the Drupal root directory on the remote host
- **uri**: the domain and optional base path of the live website
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment