ddev/ddev v0.12.0

v0.12.0: TYPO3 and Drupal6 support, allow configuration of router ports

on GitHub

Important: Use docker 17.09 until a fix comes out:

As of 30 January 2018, the latest docker versions (17.12 and 18.01) appear to hang 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.

Major changes:

• Explicit support for TYPO3 and Drupal 6 (to go with Drupal 7/8 and Wordpress, Backdrop coming soon)
• It's now possible to change the ports the router listens on to avoid conflicts with other software. (ddev can use port 8000 and 8443 instead of 80 and 443, for example)
• The database container now uses MariaDB 10.1, an upgrade from using mysql 5.5. See below under "Warnings" to see if this affects your existing projects. It does not affect new projects.

Minor changes:

• Project PHP version information added to ddev describe
• Documentation improvements

Warnings:

• 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.

Full changelog

a5789e9 Improve json output of hostname command to give explicit results (#626)
839a9cf Regression fix: Improve --show-config-location (#625)
7b11c04 Support router_http_port and router_https_port in config.yaml, fixes #481 (#622)
0a65d77 Updated build-tools to 1.5.3 (#624)
a55178d Typo3 support for ddev, fixes #570 (#613)
7dc9dc2 Make ddev config work with args when no --apptype provided, fixes #616 (#618)
071decf Bump DBTag for mariadb startup fix (#614)
c390622 Fix nightly build by removing clashing circle config stanza (#612)
0d75373 Use alpine-based mariadb container, fixes #488 (#581)
12d7137 Improve JSON output from ddev version (#596)
de3d471 Add support for drupal6 (#595)
05ee2b7 Improve regexp so "." in regex includes newline in test (#602)
1a9f075 Fix exec-host docs (#605)
1cfdd08 Update docs for remove (and project/site) fixes #599, for #526 (#600)
da31408 chore: Capitalized WordPress (#598)
fba0615 Add PHP version information to ddev describe (#592)
60f9d89 Fix TestListWithoutDir problem on Darwin (#593)