Skip to content

Commit

Permalink
lando service links (#111)
Browse files Browse the repository at this point in the history
  • Loading branch information
AaronFeledy authored May 8, 2024
1 parent d974bbb commit 633a2ed
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
2 changes: 1 addition & 1 deletion docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Before you get started with this recipe we assume that you have:

1. [Installed Lando](https://docs.lando.dev/getting-started/installation.html) and gotten familiar with [its basics](https://docs.lando.dev/cli/)
2. [Initialized](https://docs.lando.dev/cli/init.html) a [Landofile](https://docs.lando.dev/core/v3) for your codebase for use with this recipe
3. Read about the various [services](https://docs.lando.dev/core/v3/lando-service.html), [tooling](https://docs.lando.dev/core/v3/tooling.html), [events](https://docs.lando.dev/core/v3/events.html) and [routing](https://docs.lando.dev/core/v3/proxy.html) Lando offers.
3. Read about the various [services](https://docs.lando.dev/core/v3/services/lando.html), [tooling](https://docs.lando.dev/core/v3/tooling.html), [events](https://docs.lando.dev/core/v3/events.html) and [routing](https://docs.lando.dev/core/v3/proxy.html) Lando offers.

## Quick Start

Expand Down
4 changes: 2 additions & 2 deletions docs/legacy/drupal-7.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ Because of how Lando's [php service](https://docs.lando.dev/plugins/php) sets up

Said more explicitly: **if you've required `drush` via `composer` in your application then this recipe will use your `drush` and not the one you've specified in this recipes config.**

If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).
If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).

**Automatically composer install before my app starts**

Expand Down Expand Up @@ -132,7 +132,7 @@ Make sure the alias file exists within the drush folder in your app. An example

For info on how to set up your alias, please refer to the following [link](https://www.drupal.org/node/1401522) or see this [example](https://github.com/drush-ops/drush/blob/8.x/examples/example.aliases.drushrc.php).

Then configure the following [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.
Then configure the following [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.

```yml
services:
Expand Down
4 changes: 2 additions & 2 deletions docs/legacy/drupal-8.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ Because of how Lando's [php service](https://docs.lando.dec/php) sets up its [`P

Said more explicitly: **if you've required `drush` via `composer` in your application then this recipe will use your `drush` and not the one you've specified in this recipes config.**

If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).
If you are using a site-local Drush, it is also recommended to configure a [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) to automatically install Drush before your app starts up. This can prevent weird version mismatches and other issues if you are using Drush in other Lando automation like [events](https://docs.lando.dev/core/v3/events.html).

**Automatically composer install before my app starts**

Expand Down Expand Up @@ -135,7 +135,7 @@ Make sure the alias file exists within the drush folder in your app. An example

For info on how to setup your alias, please refer to the following [link](https://www.drupal.org/node/1401522) or see this [example](https://raw.githubusercontent.com/drush-ops/drush/8.x/examples/example.aliases.drushrc.php).

Then configure the following [build step](https://docs.lando.dev/core/v3/lando-service.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.
Then configure the following [build step](https://docs.lando.dev/core/v3/services/lando.html#build-steps) in your [Landofile](https://docs.lando.dev/core/v3) and `lando rebuild`.

```yml
services:
Expand Down

0 comments on commit 633a2ed

Please sign in to comment.