Hi,
Just spend an hour scanning the FAQ and htsearch entry and am obviously
missing something obvious here ...
I currently have htdig running nicely across our whole site (both internal AND
external pages). These internal and external pages are hosted across a number
of physical machines, with the logical->physical mapping being performed by
a central Solaris box using Apache (via VirtualHosts and some Reverse Proxy
configs). To a user, it appears as though our ext pages live on one box and
the int pages on another - a browser uses www.<domain> or wwwi.<domain> to
access one area or the other.
What's the neatest way to split things up into ext and int from an htdig
perspective? And (if practicable) continue to provide our "whole site"
search that currently lives in /usr/local/htdig (internal users may want
to search the lot)
I guess I could just copy my /usr/local/htdig tree so I have distinct
/usr/local/htdig_int and /usr/local/htdig_ext trees. But with that, it
looks as though I'd need to recompile for each tree because (eg) htsearch
appears to have no runtime mechanism for telling it where to source its config
- the HTML doco tells us it uses "CONFIG_DIR/htdig.conf", which I assume is
the compiled-in value?
Cheers,
Tony
Tony Sanderson - CSIRO _--_|\ [EMAIL PROTECTED]
Division of Minerals / \ tel +61 3 9545 8900 or 8799
Box 312 Clayton South \_.--.*/ fax +61 3 9562 8919
3168 AUSTRALIA v http://www.minerals.csiro.au
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
