Working with WordPress

Lando offers a configurable recipe for spinning up WordPress apps. Let's go over some basic usage.

Prefer video tutorials?

Getting Started

Before you get started with this recipe we assume that you have:

  1. Installed Lando
  2. Read up on how to get a .lando.yml

If after reading #2 above you are still unclear how to get started then try this

# Go into a local folder with your site or app codebase
# You can get this via git clone or from an archive
cd /path/to/my/codebase

# Initialize a basic .lando.yml file for my recipe with sane defaults
lando init

# Commit the .lando.yml to your git repo (Optional but recommended)
git add -A
git commit -m "Adding Lando configuration file for easy and fun local development!"
git push

For more info on how lando init works check out this.

Starting Your Site

Once you've completed the above you should be able to start your WordPress site.

# Start up app
lando start

# List information about this app.
lando info

# Optionally run composer install if needed
lando composer install

If you visit any of the green-listed URLs that show up afterwards you should be welcomed with the WordPress installation screen.

If you are installing WordPress from scratch will also want to scope out your database credentials by running lando info so you can be prepped to enter them during the installation. You will want to use internal_connection information.

Or you can read below on how to import your database.

Importing Your Database

Once you've started up your WordPress site you will need to pull in your database and files before you can really start to dev all the dev. Pulling your files is as easy as downloading an archive and extracting it to the correct location. Importing a database can be done using our helpful lando db-import command.

# Go into my app
cd /path/to/my/app

# Grab your database dump
curl -fsSL -o database.sql.gz ""

# Import the database
# NOTE: db-import can handle uncompressed, gzipped or zipped files
# Due to restrictions in how Docker handles file sharing your database
# dump MUST exist somewhere inside of your app directory.
lando db-import database.sql.gz

You can learn more about the db-import command over here.


Each Lando WordPress recipe will also ship with helpful dev utilities. This means you can use things like wp-cli, composer and php-cli via Lando and avoid mucking up your actual computer trying to manage PHP versions and tooling.

lando composer                 Run composer commands
lando db-import <file>         Import <file> into database. File is relative to approot.
lando mysql                    Drop into a MySQL shell
lando php                      Run php commands
lando wp                       Run wp-cli commands
# Search-replace the domain name
lando wp search-replace 'some.old.domain' ''

# Run composer install
lando composer install

# Drop into a mysql shell
lando mysql

# Check the app's php version
lando php -v

You can also run lando from inside your app directory for a complete list of commands.



You can also manually configure the .lando.yml file to switch php versions, toggle between apache and nginx, activate xdebug, choose a database type and version, set a custom webroot locaton and use your own configuration files.

# WordPress recipe
name: wordpress

# Start with the default WordPress recipe
recipe: wordpress

# Configure the WordPress recipe

  # See:

  # Optionally specify the php version to use.
  # If ommitted this will default to the latest php version supported by WordPress.
  # Consult the `php` service to see what versions are available. Note that all
  # such versions may not be supported in WordPress so YMMV.
  # See:
  # NOTE: that this needs to be wrapped in quotes so that it is a string
  php: '7.0'

  # Optionally specify whether you want to serve drupal via nginx or apache
  # If ommitted this will default to the latest apache
  # See:
  via: nginx

  # Optionally specify the location of the webroot relative to your approot.
  # If ommitted this will be your approot itself.
  webroot: web

  # Optionally specify the database type, this can be one of:
  #   - `mysql`
  #   - `mariadb`
  # If ommitted this will default to the latest mysql. You can additionally provide
  # a version with `type:version` but you will need to consult the documentation
  # for the correct DB service to see what versions are available
  # see:
  database: mariadb

  # Optionally activate xdebug
  # If you are having trouble getting xdebug to work please see:
  xdebug: true

  # Optionally mix in your own config files
  # If ommitted this will use "sane defaults" for your recipe type

    # For more information on setting these files check out the documentation
    # and examples
    # Docs:
    # Examples:
    server: wordpress2.conf
    # php: config/php.ini

    # For more information on setting these files check out the documentation
    # and examples for the relevant services:
    # MySQL:
    # MariaDB:
    # PostGres:
    # Examples:
    # database: config/mysql

You will need to rebuild your app with lando rebuild to apply the changes to this file. You can check out the full code for this example over here.

Environment Variables

The below are in addition to the default variables that we inject into every container. These are accessible via php's getenv() function.

# The below is a specific example to ILLUSTRATE the KINDS of things provided by this variable
# The content of your variable may differ

NOTE: These can vary based on the choices you make in your recipe config. NOTE: See this tutorial for more information on how to properly use $LANDO_INFO.


You can take advantage of Lando's events framework to automate common tasks. Here are some useful examples you can drop in your .lando.yml to make your WordPress app super slick.


  # Runs composer install and a custom php script after your app starts
    - appserver: cd $LANDO_MOUNT && composer install
    - appserver: cd $LANDO_WEBROOT && php script.php

  # Runs wp search-replace after a db import
    - appserver: wp search-replace OLDURL NEWURL

Advanced Service Usage

You can get more in-depth information about the services this recipe provides by running lando info.

Read More

Workflow Docs

Advanced Usage

results matching ""

    No results matching ""