Adds a standard Laravel configuration structure to allow the config repository to be used (and therefore, allow Scout's configuration to be cacheable).
If a consumer does NOT use config:cache at the moment, they can continue to use .env and everything will work as-is, without any changes. They may optionally use the vendor:publish command to bring their configuration setup in line with the Laravel "standards"
If a consumer uses config:cache, the must use the vendor:publish command (as per added documentation in README.md) - this will fix behaviour observed in #33
Adds a standard Laravel configuration structure to allow the config repository to be used (and therefore, allow Scout's configuration to be cacheable).
config:cacheat the moment, they can continue to use.envand everything will work as-is, without any changes. They may optionally use thevendor:publishcommand to bring their configuration setup in line with the Laravel "standards"config:cache, the must use thevendor:publishcommand (as per added documentation inREADME.md) - this will fix behaviour observed in #33Fixes #33