This question about Using an extension: Needs followup in Tasks

solr and solr-run sibdirectories

According to SolrPlugin

By default Solr listens to port 8983 on the localhost and is configured to only allow connections from localhost for security reasons. You can change these settings in

However, when I installed SolrPlugin, I got a solr directory and no solr-run directory.

I have also downloaded SolrPlugin -bin.tar.gz from SolrPlugin and note that this archive expands to a solr subdirectory.

Am I supposed to unpack the new solr directory ""over" the existing solr subdirectory? It should just merge?

Or should I have a solr-run directory? (Is there a bug in the docs or in the installed directory structure?).

-- VickiBrown - 09 Jul 2012

What I did: unpack the tar archive "over top of" the existing solr directory.

But either the docs or the installation need to change. If the docs change, a note needs to be added to say that it's ok that two archives contain the "same" subdirectory.

What is "Best Practice" here?

-- VickiBrown - 10 Jul 2012

Best Practice is to install solr in your systems servelt container (tomcat or jetty) controlled by the init process of the server.

Then use the configuration files under solr/ to configure it.

In any case you will be better of using the current sources in trunk

-- MichaelDaum - 10 Jul 2012

Again, this runs very much contrary to the documentation in the SolrPlugin page. Also, if something in svn is more current that the info/docs/code in the current release of Foswiki, that needs to be updated stat.

-- VickiBrown - 11 Jul 2012

QuestionForm edit

Subject Using an extension
Extension SolrPlugin
Status Needs followup in Tasks
Related Topics
Topic revision: r4 - 11 Jul 2012, VickiBrown
The copyright of the content on this website is held by the contributing authors, except where stated elsewhere. See Copyright Statement. Creative Commons License    Legal Imprint    Privacy Policy