[Blacklight-development] solr dir within and without rails dir?

[Matt Mitchell]

Just wanted to jump in and explain why I made 2 solr "directories". There
were a few times when our solr indexing schema/config was out of sync with
our front-end solr. I had made some changes to the front-end solr files, but
because our indexer was not using the same/up-to-date solr we ran into some
problems. So my idea was for the indexer to use the same solr as the
front-end. And by that, I mean SVN externals.

So, trunk/rails/solr is an SVN externals link to trunk/solr. But we still
have to SVN externals the blacklight_indexer stuff. If you look at the
following directory, you won't see "solr" in the listing. It gets pulled in
when you do a checkout/update:

http://blacklight.rubyforge.org/svn/trunk/rails/

Does that help?

Bob, if you want... you can sync up your indexer's solr by doing:

export SVN_EDITOR=<YOUR TEXT EDITOR>
cd blacklight_importer
svn pe svn:externals .

When your text editor opens, add this to the first line:

solr http://blacklight.rubyforge.org/svn/trunk/solr

Do a commit and you'll be good to go! Then you can start using the
blacklight_importer/solr as your solr home. Any time I make a change and
commit, you'll download the changes when you run an update. I've already
added svn:ignore to the solr/data dir.

Matt

On Fri, May 16, 2008 at 5:08 PM, Naomi Dushay <ndushay at stanford.edu> wrote:

> Bess,
>
> This is helpful information.  I think explanations in the readme is
> probably sufficient.   At this "get the prototype running, check out
> features, use local data" stage, it was more a point of curiosity as to why
> there were two solr directories.
>
> Like so many others, we are evaluating blacklight and other next generation
> disocvery environments, so understanding how to do things such as configure
> code for your institution's practices, for production vs. testing and so on
> is really helpful.
>
> - Naomi
> who got the incorrect title of the Beatles song:  "Within You Without You"
> is the correct title
>
>
> On May 16, 2008, at 12:11 PM, Elizabeth Sadler wrote:
>
>  Hi, Naomi.
>>
>> Well, you're right, it probably shouldn't come that way by default. The
>> thing is, we haven't really settled on a good "out of the box" way to run
>> blacklight. For testing purposes, you can run a copy of solr locally, and
>> that's what that solr directory inside the rails directory is doing there. I
>> think its also handy for running unit tests. However, you get greatly
>> increased performance if you can run solr on a separate server from the
>> rails side of things, and to make that easy we've split out a solr directory
>> that could easily be checked out to that other server.
>>
>> So for me, if I'm just playing around trying to see if something runs and
>> is passing tests, I fire it up and use the default (internal) solr. If I'm
>> for reals setting up a new installation, I check out rails on one machine, I
>> check out the external solr on a different machine, configure them and make
>> them talk to each other.
>>
>> Is it too confusing to have both of them in the checkout, though? Would it
>> help if we put something in the readme? I'm in the process of writing up a
>> pretty detailed description of how we set up a production instance of
>> blacklight... maybe that will also help?
>>
>> Bess
>>
>> On 16-May-08, at 2:19 PM, Naomi Dushay wrote:
>>
>>  I was just examining the blacklight code, and it appears the code I
>>> pulled down from SVN has a solr directory both inside the rails
>>> directory and also at the same level as the rails directory.  Is this
>>> intentional?
>>>
>>> - Naomi
>>> (who suddenly is thinking of the Beatles song "Across the
>>> Universe" ... within you and without you ...
>>> _______________________________________________
>>> Blacklight-development mailing list
>>> Blacklight-development at rubyforge.org
>>> http://rubyforge.org/mailman/listinfo/blacklight-development
>>>
>>
>> Elizabeth (Bess) Sadler
>> Research and Development Librarian
>> Digital Scholarship Services (DSS)
>> Box 400129
>> Alderman Library
>> University of Virginia
>> Charlottesville, VA 22904
>>
>> bess at virginia.edu
>> (434) 243-2305
>>
>>
>> _______________________________________________
>> Blacklight-development mailing list
>> Blacklight-development at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/blacklight-development
>>
>
> Naomi Dushay
> ndushay at stanford.edu
>
>
>
>
> _______________________________________________
> Blacklight-development mailing list
> Blacklight-development at rubyforge.org
> http://rubyforge.org/mailman/listinfo/blacklight-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/blacklight-development/attachments/20080516/af7556cf/attachment.html>