Local Development Stack

Owned by Catherine Armstrong (Unlicensed)
Last updated: Feb 08, 2023 by Peder Klockmann
2 min read

The local development stack allows college developers to update the theme for their College’s website. This capability should mainly be used to modify CSS for branding imagery and custom page-specific styles.

Getting Access to Your College Pantheon Site

Before using the local development stack for the first time, you will need to complete the following steps:

Mac users may use Pantheon Localdev for local development as an alternative to the following Lando instructions.

Instructions for Using Lando

Hardware requirements: Installation

  • Generate and add an SSH key to your Pantheon account.

  • Install Lando and the Docker version that comes with it. Lando v3.11.0 has been tested on Windows, Mac, and Linux. Other versions will not be supported.

  • Install Git.

Get the Code

  • Sign into the Pantheon Dashboard.

  • Select the “Organizations” tab below your username and follow the “Maricopa Community College” link.

  • Locate your Site Name and click the name to open the site dashboard.

  • Find the “Clone with Git” button and use the code to clone your site’s code in a terminal.

Running Lando

Start Lando.

lando start

Once up and running, Lando will return the site URL. Look under "APPSERVER URLS" for the address to use in your browser. It will be similar to: http://[app].lndo.site.

Download and import the site's database and content files.

lando pull --code=none --database=dev --files=dev

Logging into Drupal

Google Auth will not be available in your development environment. Use the following drush command to login with your MEID:

lando drush uli meid123456

Rebuilding the Dev Environment

When Lando stops working you may need to rebuild the service containers. Do the following procedure to wipe your Lando instance and build a fresh install. Warning: This procedure will delete your database contents and all Lando/Docker images.

Troubleshooting

Cannot Create Directory

If you encounter this Windows error after downloading and importing the site's database and content files:

Resolving this will require manually creating the symbolic link.

In Git Bash, run the following commands:

 

Proceed again with downloading and importing the site's database and content files:

 

If you have to use this fix, make sure your code edits are reflected in the /web/ folder in addition to /docroot/ to test changes locally.