There are [official docker image](https://hub.docker.com/_/solr/) for solr now. 

Unfortunately it only supports solr 5.3 (we use 4.2.1 currently).

There another [popular image](https://hub.docker.com/r/makuk66/docker-solr/) 
but it is deprecated in favor of official image and the earliest version it 
supports is 4.10.

Should we update to solr 5.3? AFAIK we're not using any fancy solr options, 
only `schema.xml` to describe solr schema, format of which did not changed 
between versions.

List of major changes can be found 
[here](https://cwiki.apache.org/confluence/display/solr/Major+Changes+from+Solr+4+to+Solr+5#MajorChangesfromSolr4toSolr5-solr.xmlFormat).

Of course we can create own solr image, but keeping up to date with versions 
would be better, I think.

And solr 5 introduces some "Ease Of Use/Operational Support" improvements which 
can be useful for this ticket specifically :)

Any concerns I'm missing?


---

** [tickets:#7907] Use standardized solr installation**

**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-4 sf-current 42cc 
**Created:** Mon Jun 29, 2015 03:25 PM UTC by Dave Brondsema
**Last Updated:** Thu Nov 05, 2015 11:35 AM UTC
**Owner:** Igor Bondarenko


We have a hacky setup for solr (both step-by-step and docker install):

* we wget solr, instead of using a system package
* we copy our schema into the solr example dir
* we run `start.jar` directly instead of a service

For docker, we should be able to use a solr image that somebody else has set 
up.  For the step-by-step we should use system packages and perhaps borrow 
ideas from the solr container's Dockerfile.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.

Reply via email to