Only do extra things in official starter kits / default laravel

[joshmanders]

Closes #410

With the addition of --using flag, we now have the ability to create userland starter kits, but unfortunately if your starter kit deviates just a little bit away from how Laravel officially does things, such as maybe the starter kit doesn't use a database at all, just a static file system, getting asked about what database you use and running commands to alter the starter based on that could be problematic. This PR only executes these prompts if you're in an official laravel starter kit or the default laravel skeleton.

[devajmeireles]

Wouldn't a better way to fix this be to check if composer.json has post-root-package-install before running it, rather than just running it on the official Laravel starter kits?

[joshmanders]

Wouldn't a better way to fix this be to check if composer.json has post-root-package-install before running it, rather than just running it on the official Laravel starter kits?

It's doing more than just executing that command. Asking for a testing suite choice, copying .env.example to .env and updating the .env file could also be issues for custom starter kits.

[taylorotwell]

I think we would need to think about this one a bit. The env stuff especially feels like something you would want to keep.

[joshmanders]

@taylorotwell

I think we would need to think about this one a bit. The env stuff especially feels like something you would want to keep.

That's a redundant extra step in the installer anyway as the official skeleton and all the starter kits already do that in the post-root-package-install