ENG/RUS   Main :: RiSearch :: RiSearch Pro :: RiCoord :: RiMap :: RiSearch PHP :: RiLax :: Forum

Introduction :: Manual :: Order :: License :: System requirements


RiSearch Pro v.3.2 Manual

© S. Tarasov


  1. Open the compressed archive you downloaded and copy everything to your cgi-bin directory.

  2. Create directories "db" for index files and "log" for query logs.

  3. Set permissions of script files and "db|log" dirs to world-readable world-executable (755 for script files and 777 for directories "db" and "log").

      Inside archive you will find several directories and scripts:

     cache/       - directory for search results caching
     db/          - directory for index files
     html_docs/   - documentation
     lib/         - directory with modules
     log/         - directory for search queries log files
     templates/   - directory for design templates
     search.php   - PHP frontend for search script
     add.pl       - script for new document indexing
     admin.pl     - admin panel
     index.pl     - indexing script
     merge.pl     - script for indexes merging
     search.pl    - searching script
     show.pl      - shows document with highlighted keywords
     spider.pl    - script for indexing via HTTP
     stat.pl      - queries statistic analysis
     update.pl    - script for indexing new or updated pages only
     riconfig.pm  - file with all configurable parameters

      Before you start, once again check main sources of errors in CGI scripts.

  1. First line of every script should begin with path to Perl in your server. Usually it is #!/usr/bin/perl. On Windows system you should write something like #!C:\PERL\5.00502\bin\MSWin32-x86-object\perl.exe, though simple #!perl should work.

  2. Unix-systems have different format of text files, than Windows. The difference is in "end of line" symbols. Therefore, you should convert your scripts in Unix format before uploading (it could be done in many text editors, like UltraEdit) or use ASCII mode in your FTP client during uploading.

  3. And check once again permission settings for all scripts (you can set them in almost all FTP clients, even if you have no access to shell). Please note that your provider may require settings for scripts permissions different from listed above.

http://risearch.org S.Tarasov, © 2000-2003