Wesley and Jonas,
today I upgraded the Lurker 1.3 installation on my Debian server to version
2.1. I encountered a few oddities and questions and want to feed them back
to you.
* The lurker-index(1) man-page talks about the "-b" flag in several
places, but this flag doesn't exist (anymore).
* README.Debian talks about "lurker-index-fc", but I think it's supposed
to read "lurker-index-lc".
* README.mailman could use a rewrite, especially since the pre-2.0 stuff
(mailman2lurker.pl, lurker-index-bin) is now history and thus
irrelevant. (This and a few other files contain a lot of bad English,
too -- no offense, Jonas.) Perhaps I can contribute something as soon
as I have worked out a good configuration setup on my system for Lurker
and Mailman.
* Can the global lurker.conf options be overridden locally in individual
frontends, such as "admin_address = webmaster@<frontend-domain>"?
Generally, the use of frontends is not well documented. :-(
* The default apache.conf says:
RewriteRule ^(attach|list|mbox|message|mindex|search|splash|thread|zap)/[^/]+$
That means that the URL paths by which Lurker is accessed will begin
with "/attach/", "/list/", etc., not with "/lurker/attach/" (or
generally "/foo/attach/"). However I don't think this is desirable, so
I tried setting the RewriteRule to ^/lurker/(attach|..., but that made
Lurker give the following error message over HTTP:
| Lurker - failed to render page:
| Bad document request (/lurker/splash/index.en.html):
| The path '/lurker' could not be resolved while attempting to
| determine which frontend the document belongs to. Perhaps a directory
| does not exist?
Is there a way to "mount" Lurker _below_ the HTTP URL path root, e.g.
at /lurker/?
Oh, and is the trailing [^/]+$ in the RewriteRule necessary for
security reasons?
* Can the message deletion UI (i.e. the button and URL) be disabled if
one doesn't want to use it? If so, how?
More when I manage to get Lurker back up running.
Julian.
(text/plain)
