Skip to content

CMS Quickstarts

Once DDEV is installed, you can quickly spin up new projects:

  1. Clone or create the code for your project.
  2. cd into the project directory and run ddev config to initialize a DDEV project.
    It automatically detects your project type and docroot—make sure it’s accurate!
  3. Run ddev start to spin up the project.
    If your project needs it, don’t forget to run ddev composer install.
  4. Import a database with ddev import-db.
  5. Optionally import user-managed files with ddev import-files.
  6. Run ddev launch to open your project in a browser, or visit the URL given by ddev start.


While you’re getting your bearings, use ddev describe to get project details, and ddev help to investigate commands.

DDEV comes ready to work with any PHP project, and has deeper support for several common PHP platforms and content management systems.


The php project type is the most general, ready for whatever modern PHP or static HTML/JS project you might be working on. It’s just as full-featured as more specific options, just without any app-specific configuration or presets.

You may even prefer to stick with this flavor despite using one of the apps DDEV supports, simply because you’d rather configure things to your own liking. Please do!

  1. Create a directory (mkdir my-new-project) or clone your project (git clone <your_project>).
  2. Change to the new directory (cd my-new-project).
  3. Run ddev config and set the project type and docroot, which are usually auto-detected, but may not be if there's no code in there yet.
  4. Run ddev start.
  5. If you’re using Composer, run ddev composer install.
  6. Configure any database settings; host='db', user='db', password='db', database='db'
  7. If needed, import a database with ddev import-db --src=/path/to/db.sql.gz.
  8. Visit the project in a browser, and then build things.


There are several easy ways to use DDEV with WordPress:


DDEV has built-in support for WP-CLI, the command-line interface for WordPress.

mkdir my-wp-site
cd my-wp-site/

# Create a new DDEV project inside the newly-created folder
# (Primary URL automatically set to `https://<folder>`)
ddev config --project-type=wordpress
ddev start

# Download WordPress
ddev wp core download

# Launch in browser to finish installation
ddev launch

# OR use the following installation command
# (we need to use single quotes to get the primary site URL from `.ddev/config.yaml` as variable)
ddev wp core install --url='$DDEV_PRIMARY_URL' --title='New-WordPress' --admin_user=admin --prompt=admin_password

# Launch WordPress admin dashboard in your browser
ddev launch wp-admin/


Bedrock is a modern, Composer-based installation if WordPress:

mkdir my-wp-bedrock-site
cd my-wp-bedrock-site
ddev config --project-type=wordpress --docroot=web --create-docroot
ddev start
ddev composer create roots/bedrock

Update the .env file in the project root for Bedrock’s WordPress configuration convention:


You can then run ddev start and ddev launch.

For more details, see Bedrock installation.

Git Clone

To get started using DDEV with an existing WordPress project, clone the project's repository. Note that the git URL shown here is just an example.

git clone
cd example-site
ddev config

You'll see a message like:

An existing user-managed wp-config.php file has been detected!
Project DDEV settings have been written to:


Please comment out any database connection settings in your wp-config.php and
add the following snippet to your wp-config.php, near the bottom of the file
and before the include of wp-settings.php:

// Include for DDEV-managed settings in wp-config-ddev.php.
$ddev_settings = dirname(__FILE__) . '/wp-config-ddev.php';
if (is_readable($ddev_settings) && !defined('DB_USER')) {

If you don't care about those settings, or config is managed in a .env
file, etc, then you can eliminate this message by putting a line that says
// wp-config-ddev.php not needed
in your wp-config.php

So just add the suggested include into your wp-config.php, or take the workaround shown.

Now start your project with ddev start

Quickstart instructions regarding database imports can be found under Importing a database.


Drupal 9 via Composer

mkdir my-drupal9-site
cd my-drupal9-site
ddev config --project-type=drupal9 --docroot=web --create-docroot
ddev start
ddev composer create "drupal/recommended-project" --no-install
ddev composer require drush/drush --no-install
ddev composer install
ddev drush site:install -y
ddev drush uli
ddev launch

Drupal 10 via Composer

Drupal 10 is fully supported by DDEV.

mkdir my-drupal10-site
cd my-drupal10-site
ddev config --project-type=drupal10 --docroot=web --create-docroot
ddev start
ddev composer create --no-install drupal/recommended-project:^10@alpha
ddev composer require drush/drush --no-install
ddev composer install
ddev drush site:install -y
ddev drush uli
ddev launch


As Drupal 10 moves from beta and to release, you’ll want to change the tag from ^10@beta to ^10.

Drupal 6/7

git clone
cd my-drupal-site
ddev config # Follow the prompts to select type and docroot
ddev start
ddev launch /install.php

Drupal 7 doesn’t know how to redirect from the front page to /install.php if the database is not set up but the settings files are set up, so launching with /install.php gets you started with an installation. You can also drush site-install, then ddev exec drush site-install --yes.

See Importing a Database.

Git Clone

git clone
cd example-site
ddev config # Follow the prompts to set Drupal version and docroot
ddev composer install # If a composer build
ddev launch



mkdir my-typo3-site
cd my-typo3-site
ddev config --project-type=typo3 --docroot=public --create-docroot --php-version 8.1
ddev start
ddev composer create "typo3/cms-base-distribution" --no-install
ddev composer install
ddev restart
ddev exec touch public/FIRST_INSTALL
ddev launch

Git Clone

git clone
cd example-site
ddev config --project-type=typo3 --docroot=public --create-docroot --php-version 8.1
ddev composer install
ddev restart
ddev exec touch public/FIRST_INSTALL
ddev launch

OpenMage/Magento 1

  1. Download OpenMage from release page.
  2. Make a directory for it, for example mkdir ~/workspace/OpenMage and change to the new directory cd ~/workspace/OpenMage.
  3. ddev config and accept the defaults.
  4. Install sample data. (See below.)
  5. Run ddev start.
  6. Follow the URL to the base site.

You may want the Magento 1 Sample Data for experimentation:

  • Download Magento Sample Data.
  • Extract the download:
    tar -zxf ~/Downloads/compressed-magento-sample-data- --strip-components=1
  • Import the example database magento_sample_data_for_1.9.2.4.sql with ddev import-db --src=magento_sample_data_for_1.9.2.4.sql to database before running OpenMage install.

OpenMage is a huge codebase, and we recommend using Mutagen for performance on macOS and traditional Windows.

Magento 2

Normal details of a Composer build for Magento 2 are on the [Magento 2 site]( You must have a public and private key to install from Magento’s repository. When prompted for “username” and “password” in composer create, it’s asking for your public and private keys.

mkdir ddev-magento2 && cd ddev-magento2
ddev config --project-type=magento2 --php-version=8.1 --docroot=pub --create-docroot --disable-settings-management
ddev get drud/ddev-elasticsearch
ddev start
ddev composer create --no-install --repository= magento/project-community-edition -y
ddev composer install
rm -f app/etc/env.php
# Change the base-url below to your project's URL
ddev magento setup:install --base-url='' --cleanup-database --db-host=db --db-name=db --db-user=db --db-password=db --elasticsearch-host=elasticsearch --admin-firstname=Magento --admin-lastname=User --admin-user=admin --admin-password=admin123 --language=en_US
ddev magento deploy:mode:set developer
ddev magento module:disable Magento_TwoFactorAuth
ddev config --disable-settings-management=false

Change the admin name and related information is needed.

You may want to add the Magento 2 Sample Data with ddev magento sampledata:deploy && ddev magento setup:upgrade.

Magento 2 is a huge codebase, and we recommend using Mutagen for performance on macOS and traditional Windows.


ddev config --composer-root=public --create-docroot --docroot=public --webserver-type=apache-fpm
ddev start
ddev composer create moodle/moodle -y
ddev exec 'php public/admin/cli/install.php --non-interactive --agree-license --wwwroot=$DDEV_PRIMARY_URL --dbtype=mariadb --dbhost=db --dbname=db --dbuser=db --dbpass=db --fullname="DDEV Moodle Demo" --shortname=Demo --adminpass=password'
ddev launch /login
In the web browser:

  • Login into your account using admin and password.

Visit the Moodle Admin Quick Guide for more information.


Moodle relies on a periodic cron job—don’t forget to set that up! See drud/ddev-cron.


Use a new or existing Composer project, or clone a Git repository.

The Laravel project type can be used for Lumen just as it can for Laravel.

mkdir my-laravel-app
cd my-laravel-app
ddev config --project-type=laravel --docroot=public --create-docroot
ddev start
ddev composer create --prefer-dist laravel/laravel
ddev exec "cat .env.example | sed  -E 's/DB_(HOST|DATABASE|USERNAME|PASSWORD)=(.*)/DB_\1=db/g' > .env"
ddev exec 'sed -i "s#APP_URL=.*#APP_URL=${DDEV_PRIMARY_URL}#g" .env'
ddev exec "php artisan key:generate"
ddev launch

In the examples above, we used a one-liner to copy .env.example as env and set the DB_HOST, DB_DATABASE, DB_USERNAME and DB_PASSWORD environment variables to the value of db.

These DDEV’s default values for the database connection.

Instead of setting each connection variable, we can add a ddev section to the connections array in config/database.php like this:

return [
    'connections' => [
        'ddev' => [
            'driver' => 'mysql',
            'host' => 'db',
            'port' => 3306,
            'database' => 'db',
            'username' => 'db',
            'password' => 'db',
            'unix_socket' => '',
            'charset' => 'utf8mb4',
            'collation' => 'utf8mb4_unicode_ci',
            'prefix' => '',
            'strict' => true,
            'engine' => null,

This way we only need to change the value of DB_CONNECTION to ddev in the .env to work with the db service.

This is handy if you have a local database installed and want to switch between the connections by changing only one variable in .env.

Using Vite

The default Laravel Vite template doesn’t work with DDEV, so you’ll need to set up a Vite server and configure Laravel to use it.

Set Up a Vite Server

Install the ddev-viteserve add-on.

ddev get torenware/ddev-viteserve
In .ddev/.env, change VITE_PROJECT_DIR=frontend to VITE_PROJECT_DIR=.

In .ddev/.env add VITE_JS_PACKAGE_MGR=npm. This tells ddev-viteserve to use npm to manage packages, and helps keep dependencies in sync.

Next add the following line to the post-install hook in your .ddev/config.yaml

        - exec: .ddev/commands/web/vite-serve
This will spin up a Vite development server on port 5173 whenever you ddev restart

Next expose your DDEV hostname by adding the following to your .ddev/config.yaml


Configuring Laravel

The default vite.config.js will not yet work with our DDEV environment. Lets start by installing the Vite and laravel-vite-plugin

ddev npm i -D laravel-vite-plugin vite
Then replace the default template with the following. Note that this script uses the exposed VITE_APP_URL from earlier
import laravel from 'laravel-vite-plugin';
import { defineConfig, loadEnv } from 'vite'

export default defineConfig(({ command, mode }) => {
    //Load the env variables that are prefixed with VITE_
    const env = loadEnv(mode, process.cwd(), 'VITE_')
    return {
        server: {
            hmr: {
            protocol: 'wss',
            host: env.VITE_APP_URL,
        plugins: [
                input: ['resources/css/app.css', 'resources/js/app.js'],
                refresh: true,
Add any plugins you need, like Vue, to the plugins array. Careful with changes to server properties that often cause CORS errors!

Finally, add the following to the head of the welcome.blade.php file:

@vite(['resources/css/app.css', 'resources/js/app.js'])


Apply the server changes and Laravel configuration by running ddev restart.

No need for npm run dev!

You don’t need to use npm run dev, since this attempts to run a local Vite server with the vite command. The ddev-viteserve add-on takes care of that Vite server for us.

You can confirm Vite’s working properly by making a quick change resources/js/app.js and seeing it reflected immediately.

Craft CMS

Craft CMS can be downloaded with Composer, or by manually downloading a zipped archive.

Composer project

Use this to create a new Craft CMS project from the official Craft starter project or a third-party starter project using Composer.

mkdir my-craft-project
cd my-craft-project
ddev config --project-type=craftcms
ddev composer create -y --no-scripts --no-install craftcms/craft
ddev start
ddev composer update
ddev craft install
ddev launch

Manual download

Use this to create a new Craft CMS project using a zipped archive.

mkdir my-craft-project
cd my-craft-project
curl -LO
unzip && rm
ddev config --project-type=craftcms
ddev start
ddev craft install
ddev launch

Git clone

Use this to migrate an existing Craft CMS project from a git repository and import a database dump.

git clone my-craft-project
cd my-craft-project
ddev config --project-type=craftcms
ddev start
ddev composer install
ddev import-db --src=/path/to/db.sql.gz
ddev launch

DDEV will automatically setup your .env so it will work properly for local development, so the default settings displayed in the ddev craft setup/welcome command can be used. Change them only if you need to override a particular setting.

If you have an existing Craft CMS DDEV project, you'll need to change the type: to craftcms in your project's .ddev/config.yaml and then do ddev restart to be able to use the ddev craft command.

If you have Craft CMS installed in a sub-directory in your project, you can add a CRAFT_CMD_ROOT environment variable to your .env file to specify a path relative to your project root where Craft CMS is installed. This defaults to ./, the project root directory.

Shopware 6

You can set up a Shopware 6 environment many ways, we recommend the following technique:

git clone --branch=6.4 my-shopware6
cd my-shopware6
ddev config --project-type=shopware6 --docroot=public
ddev start
ddev composer install
ddev exec bin/console system:setup --database-url=mysql://db:db@db:3306/db --app-url='${DDEV_PRIMARY_URL}'
ddev exec bin/console system:install --create-database --basic-setup
ddev launch /admin

Log into the admin site (/admin) using the web browser. The default credentials are username admin and password shopware. You can use the web UI to install sample data or accomplish many other tasks.

For more advanced tasks like adding elasticsearch, building and watching storefront and administration, see


To get started with Backdrop, clone the project repository and navigate to the project directory.

git clone
cd example-site
ddev config
ddev start
ddev launch

Configuration Files

The ddev config command attempts to create a CMS-specific settings file pre-populated with DDEV credentials.

For Drupal and Backdrop, DDEV settings are written to a DDEV-managed file, settings.ddev.php. The ddev config command will ensure these settings are included in your settings.php through the following steps:

  • Write DDEV settings to settings.ddev.php.
  • If no settings.php file exists, create one that includes settings.ddev.php.
  • If a settings.php file already exists, ensure that it includes settings.ddev.php, modifying settings.php to write the include if necessary..

For Magento 1, DDEV settings go into app/etc/local.xml

In Magento 2, DDEV settings go into app/etc/env.php

For TYPO3, DDEV settings are written to AdditionalConfiguration.php. If AdditionalConfiguration.php exists and is not managed by DDEV, it will not be modified.

For WordPress, DDEV settings are written to a DDEV-managed file, wp-config-ddev.php. The ddev config command will attempt to write settings through the following steps:

  • Write DDEV settings to wp-config-ddev.php.
  • If no wp-config.php exists, create one that include wp-config-ddev.php.
  • If a DDEV-managed wp-config.php exists, create one that includes wp-config.php.
  • If a user-managed wp-config.php exists, instruct the user on how to modify it to include DDEV settings.

You’ll know DDEV is managing a settings file when you see the comment below. Remove the comment and DDEV will not attempt to overwrite it! If you’re letting DDEV create its settings file, we recommended leaving this comment so DDEV can continue to manage it, and make any needed changes in another settings file.

 #ddev-generated: Automatically generated Drupal settings.php file.
 ddev manages this file and may delete or overwrite the file unless this comment is removed.

If you’re providing the settings.php or wp-config.php and DDEV is creating settings.ddev.php (or wp-config-local.php, AdditionalConfig.php, or similar), the main settings file must explicitly include the appropriate DDEV-generated settings file. Any changes you need should be included somewhere that loads after DDEV’s settings file, for example in Drupal’s settings.php after settings.ddev.php is included. (See Adding Configuration below).

Completely Disabling Settings Management

If you do not want DDEV to create or manage settings files, set disable_settings_management: true in .ddev/config.yaml or run ddev config --disable-settings-management. Once you’ve done that, it’s solely up to you to manually edit those settings.

Adding Configuration

Drupal and Backdrop: In settings.php, enable loading settings.local.php after settings.ddev.php is included—creating a new one if it doesn’t already exist—and make changes there. Wrap with if (getenv('IS_DDEV_PROJECT') == 'true') as needed.

WordPress: Load a wp-config-local.php after wp-config-ddev.php, and make changes there. Wrap with if (getenv('IS_DDEV_PROJECT') == 'true') as needed.

Listing Project Information

ddev list or ddev list --active-only current projects.

➜  ddev list
NAME          TYPE     LOCATION                   URL(s)                                STATUS
d8git         drupal8  ~/workspace/d8git          <https://d8git.ddev.local>              running
hobobiker     drupal6  ~/workspace/                                        stopped
➜  ddev list --active-only
NAME     TYPE     LOCATION             URL(s)                      STATUS
drupal8  drupal8  ~/workspace/drupal8  <>   running

You can also see more detailed information about a project by running ddev describe from its working directory. You can also run ddev describe [project-name] from any location to see the detailed information for a running project.

NAME        TYPE     LOCATION                URL                           STATUS
d9composer  drupal8  ~/workspace/d9composer  running

Project Information
PHP version:    7.4
MariaDB version 10.3


MySQL/MariaDB Credentials
Username: "db", Password: "db", Default database: "db"

or use root credentials when needed: Username: "root", Password: "root"

Database hostname and port INSIDE container: ddev-d9-db:3306
To connect to db server inside container or in project settings files:
mysql --host=ddev-d9-dbcomposer --user=db --password=db --database=db
Database hostname and port from HOST:
To connect to mysql from your host machine,
mysql --host= --port=33231 --user=db --password=db --database=db

Other Services
MailHog (https):
phpMyAdmin (https):

ssh-auth status: healthy

Removing Projects

There are two ways to remove a project from DDEV’s listing.

The first is destructive. It removes the project from DDEV’s list, deletes its database, and removes the hostname entry from the hosts file:

ddev delete <projectname>
ddev delete --omit-snapshot <projectname>

If you simply don’t want the project to show up in ddev list anymore, use this nondestructive command to unlist it until the next time you run ddev start or ddev config:

ddev stop --unlist <projectname>

Importing Assets for An Existing Project

An important aspect of local web development is the ability to have a precise local recreation of the project you’re working on, including up-to-date database contents and static assets like uploaded images and files. DDEV provides two commands to help with importing assets to your local environment.

Importing a Database

The ddev import-db imports the database for a project. Running this command will prompt you to specify the location of your database import. By default ddev import-db empties the default db database, then loads the provided dump file. Most people use it with command flags, like ddev import-db --src=.tarballs/db.sql.gz, but it can also prompt for the location of the dump if you only use ddev import-db:

ddev import-db
Provide the path to the database you wish to import.
Import path:
Importing database...
Successfully imported database for drupal8

Supported File Types

Database imports can be any of the following file types:

  • Raw SQL Dump (.sql)
  • Gzipped SQL Dump (.sql.gz)
  • Xz’d SQL Dump (.sql.xz)
  • (Gzipped) Tarball Archive (.tar, .tar.gz, .tgz)
  • Zip Archive (.zip)
  • stdin

If a Tarball Archive or Zip Archive is provided for the import, you’ll be prompted to specify a path within the archive to use for the import asset. The specified path should provide a raw SQL dump (.sql). In the following example, the database we want to import is named data.sql and resides at the top level of the archive:

ddev import-db
Provide the path to the database you wish to import.
Import path:
You provided an archive. Do you want to extract from a specific path in your archive? You may leave this blank if you wish to use the full archive contents
Archive extraction path:
Importing database...
A settings file already exists for your application, so ddev did not generate one.
Run 'ddev describe' to find the database credentials for this application.
Successfully imported database for drupal8

Non-Interactive Usage

If you want to use import-db without answering prompts, you can use the --src flag to provide the path to the import asset. If you’re importing an archive and wish to specify the path within the archive to extract, you can use the --extract-path flag in conjunction with the --src flag. Examples:

ddev import-db --src=/tmp/mydb.sql.gz
gzip -dc /tmp/mydb.sql.gz | ddev import-db
ddev import-db <mydb.sql

Database Import Notes

  • Importing from a dump file via stdin will not show progress because there’s no way the import can know how far along through the import it has progressed.
  • Use ddev import-db --target-db <some_database> to import to a non-default database (other than the default db database). This will create the database if it doesn’t already exist.
  • Use ddev import-db --no-drop to import without first emptying the database.
  • If a database already exists and the import does not specify dropping tables, the contents of the imported dumpfile will be added to the database. Most full database dumps do a table drop and create before loading, but if yours does not, you can drop all tables with ddev stop --remove-data before importing.
  • If imports are stalling or failing, make sure you have plenty of unused space (see #3360). DDEV has no problems importing large (2G+) databases, but importing requires lots of space. DDEV will show a warning on startup if unused space is getting low.

Last update: October 18, 2022