DDEV is a container-based development tool that really simplifies local development stacks. It is my primary local development tool and helps abstract away the need to build my own Docker images or Docker Compose YAML files.
My projects all use DDEV for local development. Regarding end-to-end testing, as part of my continuous integration process, I also use DDEV! This way, my scripts for running Cypress are the same locally and in my CI.
Sunday, July 5th, I did my livestream exploring DDEV-Live. DDEV-Live is the hosting counterpart of DDEV-Local. I use DDEV-Local as my local development stack, and I love its simplicity for running local environments with Docker.
This Sunday (July 5th) at 10 am, I am going to sign up for DDEV-Live and give the hosting platform a try. I am going to go from zero to launch with a fresh Drupal 9 project. I was given a special coupon code that I will give out for folks that also want to sign up for DDEV-Live!
This is the third, and final post in my series on running Drupal’s various test suites using the DDEV local development stack.
This is part two of a series on running Drupal’s testing suites on DDEV. We left off last time with trying to execute a FunctionalJavscript test and having every test case skipped because no browser emulator was available.
DDEV is a local development stack built on top of Docker. It gives you all of your environment needs without messy configured on your host machine, without needing to know Docker or configure your own containers. Which is great, and makes life easier. Instead of just using DDEV to develop your site or application locally, why not also run your tests within it?
I moved over to DDEV for my local development stack back in February. One of my favorite things is the ease of using Xdebug.
If you want to have multiple Solr indexes using Search API, you need to have a core for each index instance. For my local development stack, I use DDEV.