ddev/ddev v0.13.1

v0.13.1: php 7.2, drupal-console, backdrop drush extensions

on GitHub

Important: Use docker 17.09 until a fix comes out:

As of 13 Feb 2018, the latest stable docker version (17.12) hangs regularly when using docker-compose and bind-mounted filesystems. The docker issue is moby/moby#35933. As a result, we're using 17.09 exclusively until this can be solved upstream. Note that the "edge" version 18.02 may have the new fix in it.

Updates in v0.13.1

This minor release mostly just updates the web container now that php7.2 and xdebug play together:

• Add php 7.2 as an option, so we now support 5.6, 7.0, 7.1, and 7.2, all with xdebug.
• Add drupal-console launcher in /usr/local/bin/drupal
• Add the backdrop drush extensions, but only for backdrop projects.
• Minor fix for pantheon API parsing for some users.

Warnings about existing projects from before v0.12.0

• Existing projects should work fine with their existing .ddev/config.yaml. However, if you have a saved database for a project and you remove the config.yaml and/or update the usage of the db container, it may cause incompatibility with the upgraded container. In this case, do a ddev rm --remove-data and then start and re-import the database. (In the best case, export your database, then remove the .ddev folder, then use ddev config again to configure it, then use ddev import-db to reimport your project's database. Full details are in #615 (If you see the message "Failed to start yoursite: db service container ddev-yoursite-db: detected container restart; invalid configuration or container", that probably means you need to remove and restart.)
• To use the new config.yaml directives like router_http_port, router_https_port, the .ddev/docker-compose.yml must be deleted and the project restarted.

For both of these situations, the foolproof technique to upgrading a project is:

1. Save a database dump.
2. Use ddev rm --remove-data to remove the site's database storage.
3. Look at your .ddev/config.yaml for modifications (like post-import-db steps) and at your docker-compose.yml for modifications (unusual).
4. If there are no modifications, then remove your .ddev folder
5. Configure the site again using ddev config
6. Use ddev start to start it up
7. Use ddev import-db to reimport your saved database dump

Note that you do not have to update your project's .ddev folder at all, so no action is actually required unless you need new features like the ability to change the port the router listens on. And of course, you don't need to save away and reimport your database if that's not important.

Changes:

f3d1d3c (HEAD, tag: v0.13.1) PHP7.2 and Drush backdrop support, fixes backdrop drush support (#651)
ab468f8 Remove go-pantheon parsing of invited_by_id because it breaks and we don't use it, fixes #645