command runs "per-project"

[tyler36]

This PR moves the browsersync command to a "per-project" level.

The command should not be available if the project doesn't support ddev-browsersync.

[rfay]

Looks good to me. Project also overrides global, so shouldn't matter that we've left an orphaned one. But... I wonder if it would be worth trying to delete the global one in post_install? That also seems intrusive.

[tyler36]

I wonder if it would be worth trying to delete the global one in post_install? That also seems intrusive.

I thought about that. Most people wont even notice the change if/when they update.
People will definately notice if we deletes their files.

We could add a line to the README or maybe to the output on install?

[rfay]

Agreed - would be outstanding (and far better) to tell them what they can delete and why. For extra credit, test to see if it exists and if it does tell them to delete it.

[tyler36]

Added first draft of note.

I suspect @mattstein could improve on it.

[rfay]

I don't see the first draft @tyler36

[tyler36]

Pushed to correct branch.

[mattstein]

Added suggestions for paring this down a little! First time I’ve looked at this readme and I may need to follow on with a PR that fixes a bunch of product names and smaller nitpicks that were well out of scope here.

[tyler36]

@mattstein Thank you!