Component | Username | Password | Origin |
---|---|---|---|
Solr | solr | SolrRocks | security.json |
Quepid | [email protected] | password | quickstart.sh |
Grafana | [email protected] | password | quickstart.sh |
Keycloak | admin | password | docker-compose.yml |
MySQL | root | password | docker-compose.yml |
blockUnknown
is false as we want to let RRE run against the ecommerce
collection. We have locked down in security.json
to allow anonymous users only to hit the /ecommerce/select/ end point <-- UPDATE this isn't working.
When you bring up Solr Admin and then are redirected to Keycloak, when you register and sent back to Solr you are given the solr-admin
role.
So, connect to your smui_db
via localhost:3306
, with username root
, and password password
.
curl 'http://localhost:8983/solr/ecommerce/update?commit=true' --data-binary @solr/products.json -H 'Content-type:application/json'
We created a custom update processor to deal with date formats via:
curl http://localhost:8983/solr/ecommerce/config -H 'Content-type:application/json' -d '
{
"add-updateprocessor" :
{
"name" : "formatDateUpdateProcessor",
"class": "solr.ParseDateFieldUpdateProcessorFactory",
"format":["yyyy-MM-dd"]
}
}'
Create a user with the email [email protected]
and the password password
:
docker-compose run quepid thor user:create -a [email protected] "Demo User" password
For Quepid case, pick name
for title, and id
for identifier. Add thumb:imageUrl
to the list of fields.
docker-compose run rre mvn rre:evaluate
docker-compose run rre mvn rre-report:report
Prometheus and Grafana setup heavily inspired by https://github.com/vegasbrianc/prometheus and https://github.com/chatman/solr-grafana-docker
We update the /grafana/provisioning/dashboards/solr-dashboard_rev7.json
to replace ${DS_PROMETHEUS}
with Prometheus
We imported the dashboard https://grafana.com/grafana/dashboards/10306 for Rails. Could not get Puma metrics to be gathered by prometheus however.
We created [email protected]
/ password
in quickstart.sh
.
The two prometheus exporters run at http://localhost:9394/metrics and http://localhost:9854/metrics.
The monitoring should probably be on it's own network ;-)