Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Closes #261: Improve lando instructions in migration section of README #262

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Closes #261: Improve lando instructions in migration section of README #262

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3e89492
Added a few details to the Migration section regarding local Lando in…
Jul 26, 2024
0cb5f48
Apply suggestions from code review
joeparsons Aug 22, 2024
c1224a8
Update README.md
joeparsons Aug 22, 2024
4c406bd
Merge branch 'master' into 261-lando-for-pantheon-sites-readme
trackleft Oct 2, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 14 additions & 8 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,17 +192,23 @@ Once you've determined that a site is truly eligible to be migrated, follow thes
## Running migrations from Drupal 7 or UA Quickstart site downloaded from Pantheon, to Drupal 9 Arizona Quickstart site downloaded from Pantheon

NOTE: The `lando migrate-setup-from-pantheon` command requires that a site exists on Pantheon, since it uses terminus to find site variables on the source site.
NOTE: Instructions for how to use Lando for local development when contributing general fixes and enhancements to Quickstart (not Pantheon site specific) can be found in the [contributing guide in the main AZ Quickstart repository](https://github.com/az-digital/az_quickstart/blob/main/CONTRIBUTING.md#local-development).

From the parent directory where you want to create your local copy of the **destination**
site on Pantheon.
Create your local copy of the Pantheon **destination** site by initializing Lando inside an *empty* folder:
```
mkdir <destination_site_name>
cd <destination_site_name>
lando init --source pantheon
```
Or execute the bash commands:

```
mkdir <destinationsitename> && cd "$_"
mkdir <destination_site_name> && cd "$_"
lando init --source pantheon
```

This starts the interactive site creation tool that allows you to choose
your destination site from a list of sites created on Pantheon.
your destination site from a list of sites created on Pantheon. Select the site you are working on from the dropdown.

The next step is to start lando. After which you can go to one of the listed URLs upon
success
Expand Down Expand Up @@ -281,26 +287,26 @@ lando push -c none -d dev -f dev
Open the dev site when the push is complete, and do a spot check

```
terminus env:view <destinationsitename.env>
terminus env:view <destination_site_name.env>
```

**Always make a backup if overwriting live**

```
terminus backup:create <destinationsitename.live>
terminus backup:create <destination_site_name.live>
```

If all looks good, go ahead and deploy your migration to another environment,
overwriting that environment’s database and files.

```
terminus env:clone-content <destinationsitename.dev> <target_env> --cc -y
terminus env:clone-content <destination_site_name.dev> <target_env> --cc -y
```

Check the destination site.

```
terminus env:view <destinationsitename.live>
terminus env:view <destination_site_name.live>
```

### Clean up
Expand Down