From b3a89e8b2c445b2edaf1b652fd8c198eee6b41a4 Mon Sep 17 00:00:00 2001 From: danielspeicher <daniel.speicher@bitegra-solutions.de> Date: Fri, 15 Jan 2021 11:09:44 +0100 Subject: [PATCH] devops-tools/documentation#9 --- docs/composer/plugin/ahoy/index.md | 2 +- docs/composer/plugin/b4d/index.md | 4 ++-- docs/composer/plugin/d4d/index.md | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/composer/plugin/ahoy/index.md b/docs/composer/plugin/ahoy/index.md index 2e223bb..34a0fab 100644 --- a/docs/composer/plugin/ahoy/index.md +++ b/docs/composer/plugin/ahoy/index.md @@ -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 diff --git a/docs/composer/plugin/b4d/index.md b/docs/composer/plugin/b4d/index.md index 49ac4b8..010f48c 100644 --- a/docs/composer/plugin/b4d/index.md +++ b/docs/composer/plugin/b4d/index.md @@ -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 diff --git a/docs/composer/plugin/d4d/index.md b/docs/composer/plugin/d4d/index.md index 3ede8eb..e2e15e2 100644 --- a/docs/composer/plugin/d4d/index.md +++ b/docs/composer/plugin/d4d/index.md @@ -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 -- GitLab