<?php

return [
    'endpoints' => [
        'products' => [
            'host' => env('SOLR_HOST', '127.0.0.1'),
            'port' => env('SOLR_PORT', '8983'),
            'path' => env('SOLR_PATH', '/solr/'),
            'core' => env('SOLR_CORE', 'collection1')
        ]
    ]
];
<?php

return [
    'endpoints' => [
        'default' => [
            'host' => env('SOLR_HOST', '127.0.0.1'),
            'port' => env('SOLR_PORT', '8983'),
            'path' => env('SOLR_PATH', '/solr/'),
            'core' => env('SOLR_CORE', 'collection1')
        ]
    ]
];
Rename Solarium endpoint to clarify purpose
Rename Solarium endpoint to clarify purpose

We will be configuring Solarium through our `.env` file, not through
the provider config. Additionally, our current SolrScoutEngine follows
the Algolia example in that it uses `searchableAs`, which assumes that
each model will have it's own index (i.e. core?). I'm uncertain whether
that's how Solr is meant to work, but we intend to store all models
under a common schema anyway, so this is the first step to moving
in that direction.

https://solarium.readthedocs.io/en/stable/getting-started/#basic-usage
