On 11/02/2005 Julian Mehnle wrote: > 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.
as wesley mentioned, i wrote somehow confusing. the web cache isn't hardcoded, it's delivered to lurker via comandline/http get option. you're basicly right, you might setup more than one lurker instance with the debian lurker package installed. Simply create another configuration file, with a different web cache directory and database directory, and configure your webserver accordingly. my strongest objection against adding support for several lurker instances in debian packages was the problem that has already been raised: you'dd need a seperate instance for every private list (group) that needs a seperate authentication level. this makes easy support difficult, as there's no way to merge these authentication levels in any way. i agree with you that my package *makes it possible* to run several instances of lurker on one machine, but it doesn't support that. if lurker one time supports private lists one time i'll do my best do make usage of this feature as easy as possible, but at the moment i see no way to automate and/or facilitate this. you could write a short paragraph for README.Debian about how to realize different lurker instances, starting with a fresh debian lurker installation. or maybe this topic is complex enough to start a fresh README file? > * 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's not possible in the way you describe it. You have to use seperate database directories and seperate web cache directories (maybe nfs mount if the webserver runs on different hosts). you have to create one configuration file with seperate database directory, and a one webserver configuration section with a seperate web cache dir for every seperate instance. you can configure one authentication method for each instance. > * 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. this is what i still wait for ;) bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
