IMO the current flow is too complex; there are separate scripts:
install.sh
start_sprint.sh
start_clean.sh
for doing the basic install, then creating a work area, then starting up in the work area. I maintain this is more complex than it needs to be, so will experiment with trying to get it down to just two operations.
start_sprint.sh would combine the current start_sprint.sh and start_clean.sh. Basically, set up a directory in ~/sites and then start ddev there.
start_clean.sh would just go away; it blows away everything and starts over, but I've felt that it was confusing and unnecessary. Why not just start another sprint if you're working on a different patch?
IMO the current flow is too complex; there are separate scripts:
for doing the basic install, then creating a work area, then starting up in the work area. I maintain this is more complex than it needs to be, so will experiment with trying to get it down to just two operations.