: b) the need for a solr home directory and what that is for / what that means
There is some info aboutthis on the general SolrInstall page... http://wiki.apache.org/solr/SolrInstall which referes to example/solr (where a README.txtfile goes into more details) If you (coming from the perspective of a new user) would like to elaborate on that some more, that would be great ... new users are the best people to write intro docs and FAQs because they know from recent experience what isn't obvious. (I'm also going to add "Solr Home" to the SolrTerminology page) As for the tomcat specific stuff .... i'm of two minds on this. In general we should try to keep the container specific information on topic: using solr with thatcontainer. we can't (and shouldn't try to be) a general resource for the usage/vocabulary/configuration/quirks of every Servlet Container out there ... if someone wants to use Solr on resin, then they presumably have a reason for that and alrady know resin ... if not, we should just provide them with some handy links toget get more info about resin, and stay focused on teh core issue for us: "Solr on Resin" ... likewise for Tomcat, Jetty, websephere, whatever. On the other hand: we don't want to frustrate people. A lot of people taking on new projects have to ramp up on multiple technologies -- if someone knows they want to use Solr, therefore needs to get a servlet container up and running and for whatever reason has a specific need to use container XYZ, then we should try to give them *all* the info they need to run SOlr on XYZ< even if some of it isn't specific to Solr. I guess what I'm saying is: people should add any detail to the SolrTomcat page (and the other container pages) that's relevant to running Solr, but we should try to organize it in such a way that if you are already very knowledgable about Tomcat, you don't have to wade through a ton of stuff you already know to get to the stuff that's *really* Solr specific. -Hoss
