On Friday, November 15, 2002, at 02:46 PM, Pete Prodoehl wrote:
After you ./configure, and before you make, edit the CONFIG file so that:This is not entirely true. There are some ht://Dig distributions floating around that will use /etc by default (e.g. with some Linux distros); however when building an official ht://Dig release, the config file location defaults to a subdirectory named 'conf' that is created below whatever directory you specify as the install directory prefix.
DEFAULT_CONFIG_FILE= ${CONFIG_DIR}/htdig/htdig.conf
then it should look in the ${CONFIG_DIR}/htdig directory for the needed default htdig.conf file, and you can create other conf files as needed, so that they are all in the same place.
(I believe with 3.1.6 it just drops the htdig.conf file into /etc, but this could cause problems, so
So, you would have site1.conf, site2.conf, site3.conf in that htdig dir.Sounds like you are on the right track here.
Then you should be able to configure each of those files to point to the right place for their own html files and db files...
This should allow you to have a single set of binaries, and multiple sets of config files, templates, and db files.
you would then have to call the appropriate conf file for each site when indexing or searching.
This is mostly theoretical, as I plan on setting up a server like this, but haven't yet.
Does anyone see any problem with doing it this way? Or is there a better way?
Jim
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
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
