On Apr 23, 2006, at 9:45 PM, Julian Mehnle wrote:
> * The lurker-index(1) man-page talks about the "-b" flag in several
> places, but this flag doesn't exist (anymore).
So it does. Fixed in CVS.
> <packaging issues>
I'll leave this to Jonas. :-)
> * Can the global lurker.conf options be overridden locally in
> individual
> frontends, such as "admin_address = webmaster@<frontend-domain>"?
No. I suppose that would have been useful, though. If you want
different admins, you will need two different lurker.conf files.
Sorry. You can, however, re-use everything else via the 'include'
config option. Use the E=LURKER_CONFIG:/... stuff in the RewriteRule
to configure an alternate config.
ie:
lurker.conf.real:
... everything else
lurker.conf:
include = lurker.conf.real
admin_name = foo
lurker.conf.other
include = lurker.conf.real
admin_name = bar
RewriteRule ^(attach|list|mbox|message|mindex|search|splash|thread|
zap)/[^/]+$ /cgi-lurker/lurker.cgi [L,PT,E=LURKER_CONFIG:/etc/lurker/
lurker.conf.other,E=LURKER_FRONTEND:%{REQUEST_FILENAME}]
> Generally, the use of frontends is not well documented. :-(
All they really allow is turning on/off the selected mailing lists.
If you want to provide better documentation, I'll include it.
> * 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/").
You are mistaken. RewriteRule applies relative to the local path.
That means it matches /foo/attach/* if the directory containing the
rewrite rule is /foo in the URL path. Therefore, /lurker/attach works
fine (as it is the default debian setting!)
> 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?
That's Wes-programming-english for: don't change the RewriteRule! :-)
It's upset because you actually fed lurker the URL request for /
lurker/lurker/splash/index.en.html. It tried to enter the 'lurker'
directory twice, but couldn't, as there's only one! :-)
> Is there a way to "mount" Lurker _below_ the HTTP URL path
> root, e.g.
> at /lurker/?
Yes, leave the option unchanged. Just move the RewriteRule into the
scope of /var/www/lurker or where ever.
> Oh, and is the trailing [^/]+$ in the RewriteRule necessary for
> security reasons?
Well, I don't know of an exploit off-hand, but yes.
> * Can the message deletion UI (i.e. the button and URL) be
> disabled if
> one doesn't want to use it? If so, how?
It was supposed to work as: don't set the configuration option; left
blank -> no icon. However, it seems I somehow didn't test this! I've
made a note to fix this later when I have time to test it. For 2.1,
just edit ui/message.xsl:273-275 by deleting these lines:
<a href="javascript:trash('{server/doc-url}/zap/{summary/id}.
{$ext}');">
<img src="../imgs/trash.png" alt="{$delete-message}"
title="{$delete-messag
</a>
(text/plain)
