On 11/02/2005 Wesley W. Terpstra wrote: > I still don't like the thought of having to add authentication to lurker... > This should be apache's job. :-(
still true. > First, allow 'dbdir' in the scope of a list configuration to override the > public (global) 'dbdir' setting. This is taken relative to the last 'dbdir' > option. Then I could include a new configuration options 'webcache' and > 'frontend'. > [...] > Then, I could add some intelligence to lurker.cgi to detect which frontend > the webserver was trying to use. eg: if it was asked to generate > /var/www/lurker/lista/message/asfasfasf.html, it would determine that it > should be using the 'lista' frontend. Therefore, it would combine the two > databases in answering your requests. > > I could also add support to lurker-index to create the dbdir and webcache > directories automatically when the first message is imported. The imgs and > fmt directories would be symlinked to the global webcache directory. sounds like a solid plan! i'dd appreciate this way, it's the best i've heard so far. the only issue that comes into my mind is, what about groups? best would be to list at every frontend all accessible lists in the groups they belong to in the config. this makes it impossible to change the group (name) for one list in different frontends. but i believe that this is not needed too often. bye jonas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
