The Issue

If no ~/.ddev exists, and ddev --version is executed in a directory that is not a project, the global commands directory doesn't get created. You end up getting an error like this:

$ mv ~/.ddev ~/.ddev.bak
rfay@ub-2204:~/workspace/ddev$ ddev --version
Adding custom/shell commands failed: open /home/rfay/.ddev/commands/host: no such file or directory
ddev version v1.22.7-23-gefa8cea57

How This PR Solves The Issue

Create the global directory structure before existing the test for "am I in a project"

Manual Testing Instructions

mkdir -p ~/tmp/junk && cd ~/tmp/junk
mv ~/.ddev ~/.ddev.bak
ddev --version

You shouldn't get an error message. Don't forget to copy your ~/.ddev back into place if you care about it.

Automated Testing Overview

Related Issue Link(s)

Release/Deployment Notes