thanks, I will take a look at both of those options. That is much more clear than the info on the web site. I take it if I did the second option to index the site I would just do a rundig and pass it the different config files. One rundig job per file? Also, if I did the second option how are the databases named? do they default to the name of the config file?
Regards, Adam -----Original Message----- From: Gilles Detillieux [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 06, 2003 3:50 PM To: Adam Lipson Cc: [EMAIL PROTECTED] Subject: Re: [htdig] please point me to the FAQ for this According to Adam Lipson: > Thank you for your response. I did see that and it was definitely > clear that it could be done I'm just a newbie at this and the terse > documentation listed there is difficult to use. I was hoping that > someone had an example as to how a search like the one at the bottom > of the http://www.htdig.org web page was done with the pull down menu > obviously referencing different databases, or is that a poor assumption? > Is this one database and the URL fed to the cgi tells it not to look > in certain dirs? Yes, the search form(s) on the htdig.org site use only one config file and one database, and the pull-down list to which you refer sets the "restrict" parameter to htsearch, so that only certain subsets of the database are included. However, it would be easy to set up a similar pull-down list to select between different config files, each of which defines a different database via different database_dir attribute settings. E.g.: Search database: <select name="config"> <option value="docs">Documentation</option> <option value="mailing">Mailing Lists</option> <option value="devel">Developer information</option> </select> Then in your configuration directory, you'd need to set up the config files (e.g. docs.conf, mailing.conf, devel.conf) that define the databases. All of these could "include: common.conf" or something like that and just override the value of database_dir in each config file. Of course, you'd need to remove any prior definition of the "config" parameter from your search form as well. The default search.html has it defined as a hidden input parameter. -- Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]> Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/ Dept. Physiology, U. of Manitoba Winnipeg, MB R3E 3J7 (Canada) ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ ht://Dig general mailing list: <[EMAIL PROTECTED]> ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-general
