Re: [htdig] htdig when not server root

[David F. <az...@co...>]

Jim Cole wrote:

> On Saturday, February 22, 2003, at 05:43 PM, David Fleming wrote:
>
>> I have set up htdig v3.1.6 a total of once -  on my local machine 
>> (Debian 3.0, Apache). Everything went smoothly, and it works great.
>>
>> Now I would like to set it up twice more - #1, on a Linux/Apache web 
>> host with whom I have a shell account and CGI access, and #2, for a 
>> non-profit organization who's web site is also hosted on Linux/Apache 
>> but without shell access. They do have CGI.
>>
>> My questions (please forgive if too elemental - I did search through 
>> the archives but never found clear answers): in the case of #1, I'm 
>> planning to configure, compile, and install on my local machine in 
>> the same directory structure as on the remote server; upload the 
>> files, modify htdig.conf to suit, and go from there. Is this the 
>> right approach?
>
>
> This approach should work. However you probably want to build 
> with/against static libraries to avoid library conflicts on the 
> destination server.
>
>> In the case of #2, I'm guessing I'm hosed from the start, without a 
>> shell account. If it's possible to set up htdig under such 
>> circumstances, can anyone offer pointers? I think what I may need to 
>> do is run htdig on my server, indexing the non-profit's files, and 
>> search calls on their site will be to my server.
>
>
> If the hardware is sufficiently similar, you might be able to get away 
> with building htsearch and the required databases on your server and 
> then moving them to non-profit's site. Again, you would probably be 
> best off going with a static build for htsearch in order to avoid 
> problems with library dependencies. In this scenario, you would always 
> build, update, merge, etc. the databases on your server and then 
> upload them to the non-profit's site.
>
> Jim
>
>
Jim,

Thanks for this advice. I'll have to read up on static builds to make 
sure I understand, but I get the drift of what you're saying. In the #2 
scenario, as it happens I maintain the site and so I always have a 
complete and up-to-date local copy of the site. Sounds like your idea is 
a worth a try. Appreciate the help .... David