Skip to content
This repository was archived by the owner on Aug 4, 2023. It is now read-only.

Commit fd38432

Browse files
committed
Fix conflicts from master branch.
2 parents 09429a5 + 8a07a13 commit fd38432

File tree

2 files changed

+43
-37
lines changed

2 files changed

+43
-37
lines changed

SUMMARY.md

+1
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@
1212
* [Accessibility Testing](emulsify-drupal/emulsify-drupal/advanced-usage/accessibility-testing.md)
1313
* [Adding 3rd-party libraries](emulsify-drupal/emulsify-drupal/advanced-usage/3rd-party-libraries.md)
1414
* [Hot Reload Drupal](emulsify-drupal/emulsify-drupal/advanced-usage/hot-reload-drupal.md)
15+
* [Lando Environments](emulsify-drupal/emulsify-drupal/advanced-usage/lando-environments.md)
1516
* [FAQ](emulsify-drupal/emulsify-drupal/faq/README.md)
1617
* [Upgrading](emulsify-drupal/emulsify-drupal/faq/upgrading.md)
1718

emulsify-drupal/emulsify-drupal/advanced-usage/lando-environments.md

+42-37
Original file line numberDiff line numberDiff line change
@@ -2,9 +2,10 @@
22
description: Use Lando to make your development environment portable
33
---
44

5-
# Lando
5+
# Lando Environments
66

77
### Why use Lando?
8+
89
1. Standardizing local environments is simple and effective.
910
2. Your development environment is portable, so you only need Docker and Lando to develop.
1011
3. Complicated infrastructure can be stood up quickly.
@@ -14,40 +15,42 @@ description: Use Lando to make your development environment portable
1415

1516
### Dependencies
1617

17-
- [Docker](https://docs.docker.com/get-docker/)
18-
- [Lando](https://lando.dev/download/)
18+
* [Docker](https://docs.docker.com/get-docker/)
19+
* [Lando](https://lando.dev/download/)
1920

2021
### Basic Lando stack
2122

22-
1. The `drupal9` recipe can handle most the work for us
23-
```yaml
24-
recipe: drupal9
25-
```
26-
2. Both NodeJS and NPM needs to be available at a project level. Using npm the emulsify cli command can also be installed. This and npm can both be made available via Lando tooling.
27-
```yaml
28-
services:
29-
appserver:
30-
build_as_root:
31-
- apt update -y && apt install -y apt-transport-https build-essential unzip
32-
- curl -sL https://deb.nodesource.com/setup_16.x | bash -
33-
- apt-get install -y nodejs
34-
- chown -R www-data /usr/lib/node_modules
35-
- chown -R www-data /usr/bin
36-
- npm install -g npm
37-
- npm install -g @emulsify/cli
38-
...
39-
tooling:
40-
node:
41-
service: appserver
42-
npm:
43-
service: appserver
44-
emulsify:
45-
service: appserver
46-
```
23+
1. The `drupal9` recipe can handle most the work for us
24+
25+
```yaml
26+
recipe: drupal9
27+
```
28+
3. Both NodeJS and NPM needs to be available at a project level. Using npm the emulsify cli command can also be installed. This and npm can both be made available via Lando tooling.
29+
30+
```yaml
31+
services:
32+
appserver:
33+
build_as_root:
34+
- apt update -y && apt install -y apt-transport-https build-essential unzip
35+
- curl -sL https://deb.nodesource.com/setup_16.x | bash -
36+
- apt-get install -y nodejs
37+
- chown -R www-data /usr/lib/node_modules
38+
- chown -R www-data /usr/bin
39+
- npm install -g npm
40+
- npm install -g @emulsify/cli
41+
...
42+
tooling:
43+
node:
44+
service: appserver
45+
npm:
46+
service: appserver
47+
emulsify:
48+
service: appserver
49+
```
4750
3. Emulsify needs port `6006` to be available for StorybookJS and port `32778` to be available for [Hot Reload](./hot-reload-drupal.md).
4851

49-
By adding proxy address for browsersync.example.lndo.site and storybook.example.lndo.site that point to the ports needed, those applications can be accessible by navigating to the addresses (without the ports, like this: `http://storybook.example.lndo.site`) from outside the container services.
50-
52+
By adding proxy address for browsersync.example.lndo.site and storybook.example.lndo.site that point to the ports needed, those applications can be accessible by navigating to the addresses (without the ports, like this: `http://storybook.example.lndo.site`) from outside the container services.
53+
5154
Since we are using proxies instead of forwarding ports directly, multiple projects can make use of these ports simultaneously.
5255
```yaml
5356
proxy:
@@ -104,13 +107,15 @@ tooling:
104107
```
105108

106109
### Setup
107-
1. Run `composer create-project drupal/recommended-project my-project`
108-
See [Starting a Site Using Drupal Composer Project Templates](https://www.drupal.org/docs/develop/using-composer/starting-a-site-using-drupal-composer-project-templates) for more information on setting up a Drupal project with Composer.
110+
111+
1. Run `composer create-project drupal/recommended-project my-project` See [Starting a Site Using Drupal Composer Project Templates](https://www.drupal.org/docs/develop/using-composer/starting-a-site-using-drupal-composer-project-templates) for more information on setting up a Drupal project with Composer.
109112
2. Add the above lando.yml file to the project
110113
3. Run `lando start`
111114
4. After it builds you can then run these commands:
112-
- `lando node`
113-
- `lando npm`
114-
- `lando emulsify`
115-
- `lando drush`
116-
5. Follow the [Inside a Composer-Based Drupal Instance](https://www.drupal.org/docs/develop/using-composer/starting-a-site-using-drupal-composer-project-templates) steps to complete setting up Emulsify Drupal.
115+
116+
* `lando node`
117+
* `lando npm`
118+
* `lando emulsify`
119+
* `lando drush`
120+
121+
1. Follow the [Inside a Composer-Based Drupal Instance](emulsify-drupal/emulsify-drupal#inside-a-composer-based-drupal-instance) steps to complete setting up Emulsify Drupal.

0 commit comments

Comments
 (0)