Jonas Meurer wrote:
> [...] you'll have to install seperate instances of lurkers binary to
> configure different htdocs (webcache) directories as well. therefore i
> see currently no possibility to run more than one lurker instance with
> the debian lurker package installation.
Huh? Why is that? Is the web cache directory hard-coded in the Lurker
binary? Or what do you mean with "instance"? AFAIK Lurker hasn't been
using a daemon for quite a while, if that's what you mean (but I guess you
knew that). Now I'm confused.
> if you need to split the archive into private and public lists, please
> contact [EMAIL PROTECTED] I've already requested this
> feature, but there are still some residual issues that have to be
settled.
>
> the biggest problem is how to connect these two archives? do you need to
> have access to all lists in the private area? or would you split the
> archives without any connection?
>
> what about that situation: you have 5 public and 5 private lists.
> now the first private list has 20 subscribers, second, third and fourth
> each 30 and the fifth private list has 40 subscribers.
>
> remember, you need a unique account for every subscriber of every list.
>
> every private list would need a seperate private lurker instance here,
> wouldn't it?
>
> to make it even more complicated, what about people who have access to
> more than one private list? should they have one account for all, or one
> account for each of the lists?
I do have read the various related threads in the lurker-users list
archives.
This is what I'd like to have, although perhaps it might not be doable
with Lurker without knocking over its general design:
* It should be possible to run multiple sites (domains / Apache vhosts),
i.e. essentially separate groups of list web archives. These may very
well generally run from the same database, but should be able to
appear as separate groups of lists on the different web sites.
E.g. the cookmaster-pro-users list archive should appear on
http://www.cookmaster-pro.com/lurker, but not on
http://www.lawnmower-pro.com/lurker, even if everything runs on the
same physical host.
AFAICT this is already possible with Lurker (but how?).
* It should be possible to define separate access to each private list
archive. If this means that users have to authenticate multiple times
to access multiple private list archives, then so be it. I agree with
Wesley that authentication should be handled by the web server, so
admins can choose what auth method to use. This means that it must be
possible for individual private list archives to be accessed from
different, <Location(Match)>-matchable URL paths.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
