Add a `gdk doctor` command
gdk doctor
would work simialarly to brew doctor
where it would inspect the current state of things within the gdk
and attempt to make suggestions to fix known, common issues that can occur.
But I hear you ask, shouldn't we fix some of these known common issues that can occur? Yes, as much as possible we should, but issues relating to Ruby gems that depend on system libraries for example are known to be a problem from time to time and something we can't easily fix with the GDK.
gdk doctor
could do the following:
- Run
rake preflight-checks
- Run
gdk diff-config
- Advise if the GDK is out-of-date
- Advise of current service status (
gdk status
for now?) - Test gems that depend on system libraries that have been known to cause issues
- Outstanding DB migrations
- Look for permission problems
We could also suggest creating an Issue, including the output of gdk supportpack.
Edited by Ash McKenzie