Frequently-Asked Questions (FAQ)¶
- What operating systems will DDEV-Local work with?
- DDEV-Local works nearly anywhere Docker will run, including macOS, Windows 10/11 Pro/Enterprise, Windows 10/11 Home, and every Linux variant we've ever tried. It also runs in many Linux-like environments, for example ChromeOS (in Linux machine) and Windows 10/11's WSL2. In general, DDEV works the same on each of these platforms, as all the important work is done inside identical Docker containers.
- Do I lose my data when I do a
- No, you don't lose data in your database or code with any of these commands. Your database is safely stored on a docker volume.
- How does my project connect to the database?
ddev describegives full details of how to connect to the database. Inside the container the hostname is 'db' (NOT 127.0.0.1). User/password/database are all 'db'. For connection from the host, see
- How can I troubleshoot what's going wrong?
- See the troubleshooting, Docker troubleshooting and Xdebug troubleshooting sections of the docs.
- Do I need to install PHP or Composer or Nginx or nodejs/npm on my computer?
- Absolutely not. All of these tools live inside DDEV's docker containers, so you need only Docker and DDEV. This is especially handy for Windows users where there's a bit more friction installing those tools.
- How do I get support?
- See the (many) support options, including Discord, Stack Overflow and others.
- How can I get the best performance?
- Docker's normal mounting can be slow, especially on macOS. See the Performance section for speed-up options including Mutagen and NFS mounting.
- How can I check that Docker is working?
- The Docker Installation docs have a full Docker troubleshooting section, including a single
docker runcommand that will verify whether everything is set up.
- Can I run DDEV and also other Docker or non-Docker development environments at the same time?
- Yes, you can, as long as they're configured with different ports. But it's easiest to shut down one before using the other. For example, if you use Lando for one project, do a
lando poweroffbefore using DDEV, and then do a
ddev poweroffbefore using Lando again. If you run nginx or apache locally, just stop them before using DDEV. More information is in the troubleshooting section.
- How can I contribute to DDEV-Local?
- We love contributions of knowledge, support, docs, and code, and invite you to all of them. Make an issue or PR to the main repo. Add your external resource to awesome-ddev. Add your recipe or HOWTO to ddev-contrib. Help others in Discord and Stack Overflow. Follow the governance issue to learn about financial support possibilities.
- How can I show my local project to someone else?
- It's often the case that we want a customer or coworker to be able to view our local environment, even if they're on a different machine, network, etc. There are several ways to do this.
ddev shareis one of the ways - it provides a link that anyone can view and so they can interact with your local project while you allow it. See
ddev share -hfor more information. It does require an account on ngrok.com.
- Can I use additional databases with DDEV?
- Yes, you can create additional databases and manually do whatever you need on them. They are automatically created if you use
--target-db, for example
ddev import-db --target-db=extradb --src=.tarballs/extradb.sql.gz. You can use
ddev psqlfor random queries, or also use the mysql/psql clients within
ddev ssh -s dbas well.
- Can different projects communicate with each other?
Yes, this is commonly required for situations like Drupal migrations. For the web container to access the db container of another project, use
ddev-<projectname>-dbas the hostname of the other project. For example, in project1, use
mysql -h ddev-project2-dbto access the db server of project2. For HTTP/S communication you can 1) access the web container of project2 directly with the hostname
ddev-<project2>-weband port 80 or 443:
curl https://ddev-project2-webor 2) Add a .ddev/docker-compose.communicate.yaml which will allow you to access the other project via the official FQDN.
- How do I make DDEV match my production webserver environment?
- You can change the PHP major version and choose between nginx+fpm (default) and apache+fpm and choose the MariaDB/MySQL/Postgresql version add extra services like solr and memcached. You will not be able to make every detail match your production server, but with database server type and version, PHP version and webserver type you'll be close.
- How do I completely destroy a project?
ddev delete <project>to destroy a project. By default, a
ddev snapshotof your database is taken, but you can skip this using
ddev delete --omit-snapshotor
ddev delete --omit-snapshot -y, see
ddev delete -hfor options. It's up to you to then delete the code directory.
- I don't like the settings files or gitignores that DDEV creates. What can I do?
You have a couple of options that work well for most people:
Use project type "php" instead of the type of your CMS. "php" just means "Don't try to create settings files and such for me.". The "php" type works great for experienced developers.
"Take over" the settings file or .gitignore by deleting the line "#ddev-generated" in it (and then check in the file). If that line is removed, ddev will not try to replace or change the file.
- How can I change the name of a project?
- Use this process: 1. Export the database of the project:
ddev export-db --file=/path/to/db.sql.gz2.
ddev delete <project>. By default this will make a snapshot, which is a nice safety valve. 3. Rename the project,
ddev config --project-name=<new_name>4.
ddev import-db --src=/path/to/db.sql.gz
- How can I move a project from one directory to another?
ddev stop --unlist, then move the directory, then
ddev startin the new directory.
- How can I move a project from one computer to another?
- Follow this procedure: 1.
ddev start && ddev snapshot2.
ddev stop --unlist3. Move the project directory to another computer any way you want. 4. On the new computer,
ddev start && ddev snapshot restore --latest5. Optionally, on the old computer,
ddev delete --omit-snapshotto get rid of the database there.
- How can I move a project from traditional Windows to WSL2?
- This is exactly the same as moving a project from one computer to another, see above. Make sure you move the project into a native filesystem in WSL2, most likely /home.
- DDEV-Local wants to add a hostname to /etc/hosts but I don't think it should need to.
- If you see "The hostname
is not currently resolvable" and you can
ping <hostname>, it may be that DNS resolution is slow. DDEV doesn't have any control of your computer's name resolution, so doesn't have any way to influence how your browser gets an IP address from a hostname. It knows you have to be connected to the Internet to do that, and uses a test DNS lookup of
.ddev.site as a way to guess whether you're connected to the internet. If it is unable to do a name lookup, or if the hostname associated with your project is not *.ddev.site, it will try to create entries in /etc/hosts, since it's assuming you can't look up your project's hostname(s) via DNS. If your internet (and name resolution) is actually working, but DNS is slow, just
ddev config global --internet-detection-timeout-ms=3000to set the timeout to 3 seconds (or higher). Seeissue link for more details. (If DNS rebinding is disallowed on your network/router, this won't be solvable without network/router changes. Help here and here.) For more detailed troubleshooting information please see the troubleshooting section.
- How can I configure a project with the defaults without hitting
a bunch of times?
- Just use
ddev config --autoand it will choose docroot and project type based on the discovered code. If it gets anything wrong (just look at
.ddev/config.yaml) you can change that at any time using various
ddev configcommands or just by editing the
- Why do I get a 403 or 404 on my project after
- The most likely reason for this is that the docroot is misconfigured, or there's no index.php or index.html file in the docroot. Take a look at your .ddev/config.yaml and see what is there for the docroot. It should be a relative path to where your index.php is.
- Why do I see nginx headers when I'm configured to use
- Apache runs in the web container but when you use the
http://*.ddev.siteURL, it goes through ddev-router, which is an nginx reverse proxy, and that's why you see the nginx headers. But rest assured you are using Apache. More detail in Stack Overflow answer
- Why does
ddev startfail with "error while mounting volume, Permission denied"?
- This almost always means that you have NFS enabled in your project, but NFS isn't working on your machine. Start by completely turning NFS off for your projects with
ddev config --nfs-mount-enabled=false && ddev config global --nfs-mount-enabled=false. Then later, go get NFS working. NFS can be a big performance help on macOS and traditional Windows, and not needed on Linux or Windows WSL2.
- How can I install a specific version of DDEV?
If you want to use a different version of DDEV, you easily get a different version. If you're using homebrew,
brew unlink ddevfirst, to get rid of the version you have there. Then use one of these options:
- Download the version you want from the releases page and place it somewhere in your
- Use the install_ddev.sh script with the version number argument. For example, if you want v1.18.3-alpha1, use
curl -fsSL https://raw.githubusercontent.com/drud/ddev/master/scripts/install_ddev.sh | bash -s v1.18.3-alpha1
- If you want the very latest, unreleased version of ddev, use
brew unlink ddev && brew install drud/ddev/ddev --HEAD.
- Download the version you want from the releases page and place it somewhere in your
- How can I back up or restore all databases of all projects?
- You can back up all projects that show in
ddev snapshot -a. This only snapshots projects that are shown in
ddev listthough, so if you have other projects that aren't shown, you'd need to start them so they'd be registered in
- How can I contribute financially to the DDEV project?
- Thanks for asking! Contributions can be done via GitHub Sponsors. They go to the Localdev Foundation and are used for infrastructure and supporting development.