Hello,
now my setup is working. I have lurker 2.1 running on Debian unstable.
/etc/lurker/apache.conf includes archive1/apache.conf and
archive2/apache.conf. Those alias /lurker-archiveX to
/opt/ibr/var/www/lurker/archiveX, define that directory, and set CONFIG
to /etc/lurker/archiveX/lurker.conf. The latter has dbdir of
/opt/ibr/var/lib/lurker/archiveX and frontend of
/opt/ibr/var/www/lurker/archiveX. This directory contains a copy of
/var/www/lurker. /etc/mail/aliases has lines like 'some-list:
"|/usr/bin/lurker-index -c /etc/lurker/archiveX/lurker.conf -l some-list
-m"'.
I started with creating a .htaccess file in
/opt/ibr/var/www/lurker/archiveX:
AuthType Basic
AuthName lurker
AuthUserFile /etc/apache2/passwd
Require valid-user
This didn't work. My expectation was that when I try to access
https://server/lurker-archiveX/, apache should have required
authentication before serving
/opt/ibr/var/www/lurker/archiveX/index.html. But the page is served
without the browser asking anything. Why didn't it do what I wanted it
to, and how should I set that up properly?
Thanks in advance,
Baurzhan.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Lurker-users mailing list
Lurker-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lurker-users