Configuration
In order for data source queries to work, the Cook must be correctly configured to access Solr. If you used the setup tool to create a Docker-based configuration for you, then everything should be OK already and you can skip this section.
If your cook is running on bare metal or if data sources are not working
then open your cook-config.yaml
for editing and make
sure the following section is filled out correctly:
recipedata extensions - name: '@escenic/cue-front-extension-datasources' config: queries: /srv/recipe/datasources/ endpoint: 'http://my-escenic.com:8080/webservice/' solr: 'http://my-escenic.com:8983/editorial'
The entries you need to fill out are:
endpoint
-
The URL of your Content Engine web service, including a final
/
character. solr
-
The URL of your Solr core. Solr is often installed on the same host as the Content Engine, but it does not have to be. By default Solr listens on port 8983, but it can have been set up to use a different port. The final part of the URL is the name of the Solr core that is to be used. In a production environment, the data source extension should always be configured to use Solr's
presentation
core. In a development environment, however, it is often the case that nopresentation
core is available since a default Content Engine installation does not include one. So for development purposes, use theeditorial
core if nopresentation
core is available.