On a Quicksprint install flow and using a fresh Windows 10 Home machine (no previous Docker or ddev installation), start_sprint.sh fails after running install.sh.
On Windows, Quicksprint installs ddev using the Windows installer, which states that ddev may not be present in the path until a new terminal session has started. When Quicksprint is the first time a user has installed ddev, this is true, and all invocations of ddev in the start_sprint.sh script will fail.
A workaround is to start another terminal session after install.sh has completed. A more permanent and much more user-friendly fix is to ensure the PATH has been updated to include the ddev before install.sh completes.
On a Quicksprint install flow and using a fresh Windows 10 Home machine (no previous Docker or ddev installation), start_sprint.sh fails after running install.sh.
On Windows, Quicksprint installs ddev using the Windows installer, which states that ddev may not be present in the path until a new terminal session has started. When Quicksprint is the first time a user has installed ddev, this is true, and all invocations of
ddevin the start_sprint.sh script will fail.A workaround is to start another terminal session after install.sh has completed. A more permanent and much more user-friendly fix is to ensure the PATH has been updated to include the
ddevbefore install.sh completes.