New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make sure that ~/.ddev exists very early, fixes #358 #380
Conversation
4ed2c6f
to
9809ca1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The functionality here looks great, but it feels like this could really use a test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on Windows, seems to work as advertised. 👍
9809ca1
to
87a8dcb
Compare
Thanks for the coaching on how to get a test in there @beeradb - I think this will do it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
woohoo! Thanks so much for adding a test, makes me feel much better about this not popping up again.
Reading through the code everything looks good. Approving assuming the pending tests pass.
The Problem:
We have a couple of ways that ~/.ddev might not get created at the right time and it's absolutely essential for both mounts (mysql health) and updatecheck.
The Fix:
Create ~/.ddev in root.go at the very beginning before the updatecheck.
The Test:
rm -r ~/.ddev and then
ddev start
This should be tested explicitly on windows.
Automation Overview:
Adds TestCreateGlobalDdev as a test - it changes the $HOME environment variable in order to much with ~/.ddev without breaking the user's system.
Related Issue Link(s):
OP #358
Release/Deployment notes: