github ddev/ddev v1.15-alpha4
v1.15-alpha4: Fix "live" command, automatic release publishing

latest releases: v1.23.5, feature_install-ddev_v1.23.5, v1.23.4...
pre-release4 years ago

Installation/Upgrade

See the installation instructions for details, but it's easy:

  • Please stop all projects first, this does no harm: ddev poweroff
  • If you have custom configuration, especially pinned image specifications in your .ddev/config.yaml, please remove it for now.
  • macOS Homebrew and Linux Linuxbrew (ddev-edge channel only): brew install drud/ddev-edge/ddev or just brew upgrade drud/ddev-edge/ddev ). (You may need a brew update for homebrew to find the new release.)
  • Windows: Use choco upgrade -y --pre ddev to get this one, or download the ddev_windows_installer below.
  • And anywhere, you can just download the tarball or zipball, untar or unzip it, and place the executable in your path where it belongs.

Key Features of v1.15-alpha4

From earlier alpha releases

  • Laravel support! Thanks @NBZ4live ! You can now ddev config --project-type=laravel, see Laravel quickstart
  • The 'live' command allows you to use ddev live list sites and all other commands without having to install ddev-live locally.
  • zsh and oh-my-zsh completions, see docs
  • Integration with DDEV-Live hosting. See ddev-live integration docs for instructions to use ddev config ddev-live and ddev pull
  • The ddev-live client is included inside the web container, which means that you can use it there at any time and on any platform, including Windows.
  • MariaDB 10.5 support
  • The default mysql collation changes to utf8mb4_general_ci
  • The ddev-webserver docker image is down in size from 577MB to 417MB, 72% of its previous size, without losing any features.

Smaller changes

  • ddev exec will now find binaries/scripts in /var/www/html/vendor/bin, thanks @atomicptr !
  • Several small bugfixes
  • ddev-webserver is marching toward using the same basic docker images as DDEV-Live uses
  • ddev import-db will now ignore any USE <database> or CREATE DATABASE <database> statements in your imported database dump. For most people and most situations this is just fine, and database dumps should really never have those statements in them.

Caveats

  • ddev import-db will now ignore any USE <database> or CREATE DATABASE <database> statements.
  • ddev exec and exec hooks now check for errors and pipe failures by adding a set -eu -o pipefail onto the front of bash statements. It is possible that this will make exec hooks or ddev exec commands fail that should always have failed.

Commits since v1.14.3

1d64b85 Automate releases to Homebrew, Chocolatey, and AUR, fixes #2213 (#2301)
93b4008 Improve buildkite-agent setup instructions for Windows (docs only) (#2299)
b266ed6 Make sure that Exec() runs commands with bash error checking, especially pipefail (#2295)
6d8df73 Restore custom "live" command (#2296)
0dab776 Fix broken links on Extending and Customizing (#2298)
53a9ef1 Improve instructions for running macos_ddev_nfs_setup.sh (docs) (#2292) [skip ci][ci skip]
5806555 Update Drupal 8 quickstart [skip ci][ci skip] (#2294)

Don't miss a new ddev release

NewReleases is sending notifications on new releases.