As for seeding data into the demo. I think we should include a script that will load some sample data. Users can optionally run that script to get started quickly. But we should also include instruction and sample files on how to load in custom data. This way users can load in data that is more meaningful to them and see the revalency in action.
Bill On 2/14/06, Ian Holsman <[EMAIL PROTECTED]> wrote: > > Yonik Seeley wrote: > > On 2/14/06, Doug Cutting <[EMAIL PROTECTED]> wrote: > >> The demo should be included in the standard download. > > > > By "standard download" do you mean binary distribution, or the svn > repository? > > I'm not sure what a full binary distribution should look like yet... > > We had something internally, but it's too tied up in our internal > > tools. > > > >> Why not use Jetty instead of Tomcat, since it's so much smaller? > > > > It it's checked in to subversion, I agree that Jetty is probably a > > better way to go. > > > > I was thinking of Tomcat at first since some people will start with > > the demo and modify it to create their own projects, and I thought > > that they might be better served by Tomcat since it's the most > > standard. > > > > -Yonik > > > > for the demo, I agree jetty as it is just easier to get downloaded and > running. > > but you do bring up another point (for later down the track). > > Having a fully configured SolR server which you could just download, use > a self-contained webapp to configure the lucene data store and other > config bits, and then have it start accepting requests (for a > small/medium site) would be fantastic. > > If you could get a average IT-professional (not a java/lucene guru) able > to get this up&running for his boss in less than half an hour you will > be very popular. >
