fix mem_lookup with values which include characters which can be interpreted as regexes

[webpac] / global.conf

diff --git a/global.conf b/global.conf
index d965717..485fee7 100644 (file)
--- a/global.conf
+++ b/global.conf
@@ -2,19 +2,32 @@
 
 [global]
        # define database to use for indexes
-       dbi_dbd=Pg
-       dbi_dsn=dbname=webpac-dev
+#      dbi_dbd=Pg
+#      dbi_dsn=dbname=webpac-dev
+
+       dbi_dbd=SQLite
+       dbi_dsn=dbname=/data/webpac/index.sqlite
+
        dbi_user=dpavlin
-       dbi_passwd=xx
+       dbi_passwd=""
 
        # display progress bar indicator (default is no)
-       #show_progress=1
+       show_progress=1
+
+       # Filter characters before feeding them to swish. If you don't use
+       # this file, implementation will fall-back to passing through
+       # original charset, and if you have anything other than plain
+       # 7-bit ascii in your data, your words will end-up splitted in
+       # index on 8-bit characters and you won't be able to find them!
+       my_unac_filter = /data/webpac/my_unac_string.pm
 
 [webpac]
        # path to template html files
        template_html = /data/webpac/template_html
        # charset encoding for template file *and* users (default iso-8859-1)
        charset = ISO-8859-2
+       # locale to use (for sorting, uc/lc) (default hr_HR)
+       locale = hr_HR
        # path to swish binary (default /usr/bin/swish-e)
        swish = /usr/bin/swish-e
        # path to index file
@@ -29,4 +42,7 @@
        # like "&" would work. However, larger values also make sense to produce
        # more relevant hits on words like "to", "at" etc.
        min_wildcard = 2
+       # master template which will be used to enable global design changes
+       # (it will replace ##webpac## in this template with output of webpac)
+       template = /data/webpac/public_html/template.html