Feature Request
Describe your use case and the problem you are facing
I reach for wp doctor whenever a site is misbehaving, and I want a quick, repeatable read on its health. The thing is that it's a separate package, so it's almost never already on the server where I actually need it.
Sometimes I can install it, but more often, it doesn't work due to hardened hosting. On secured hosts that limit outgoing connections, wp package install simply can't run because it can't download the package from the internet. On other setups, e.g., shared hosts, installing WP-CLI packages might fail due to file system permission restrictions. So on these locked-down (production) servers where diagnostics matter most, installing doctor isn't possible at all.
Describe the solution you'd like
Has bundling doctor-command into the default Phar been considered, and if so, what was the reasoning against it?
From the outside, the cost looks low. I assume there's history I'm missing here; is it mainly a maintenance or scope concern? (I saw the note in wp-cli/handbook#574 that it's not bundled and not heavily maintained.)
Thank you!
Feature Request
Describe your use case and the problem you are facing
I reach for
wp doctorwhenever a site is misbehaving, and I want a quick, repeatable read on its health. The thing is that it's a separate package, so it's almost never already on the server where I actually need it.Sometimes I can install it, but more often, it doesn't work due to hardened hosting. On secured hosts that limit outgoing connections,
wp package installsimply can't run because it can't download the package from the internet. On other setups, e.g., shared hosts, installing WP-CLI packages might fail due to file system permission restrictions. So on these locked-down (production) servers where diagnostics matter most, installing doctor isn't possible at all.Describe the solution you'd like
Has bundling
doctor-commandinto the default Phar been considered, and if so, what was the reasoning against it?From the outside, the cost looks low. I assume there's history I'm missing here; is it mainly a maintenance or scope concern? (I saw the note in wp-cli/handbook#574 that it's not bundled and not heavily maintained.)
Thank you!