Wesley W. Terpstra wrote:
> Julian Mehnle wrote:
> > * 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.
Hmm, too bad. That essentially means I'll have to revert to the "one conf
per frontend" setup that I was using with Lurker 1.3 (with the exception
that I can now use a single combined database for everything). Not a big
problem, but perhaps you could allow global config options like "admin_
address" etc. to be added to "frontend" sections as overrides of the global
settings in the next release?.
> > 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.
I'll see what I can make up. It'll take some time, though, as I'm pretty
busy at the moment.
> > * 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: [...]
>
> That's Wes-programming-english for: don't change the RewriteRule! :-)
> [...] Just move the RewriteRule into the scope of /var/www/lurker or
> where ever.
Does that mean that
| <Directory ...>
| RewriteRule ^(...
| </Directory>
is the only way to get it working, and that a global RewriteRule outside
any <Directory>/<Location> sections won't work? It's not a big issue
either, but I'm irritated given that it worked with Lurker <2.0 (and this
was how I had it configured).
In any case, thanks for explaining the error message and for the other
answers and for your great work on Lurker! :-)
Julian.
(text/plain)
