To allow third-party plugins for webconf, I would like to propose the following:
webconf "plugins" have the name "LWP" (Leaf [Webconf | Web] [Plugin | Package]) The format is a gzipped tar archive with /var/webconf/www/*.cgi /var/webconf/conf/*.webconf For instance, the dropbear.lwp could contain /var/webconf/www/dropbear.cgi /var/webconf/conf/dropbear.webconf A /etc/init.d/webconf script could then scan the package disks for LWP files and install them at startup. For flexibility, I'd like to support selecting which webconf's one loads. For instance, if booting from a floppy/CD combination, it may not be desireable to load ALL the .lwp's from the CD. The proposal is to add an optional LWP= directive to leaf.cfg, just like LRP=; If LWP is defined in leaf.cfg, then that is the list of web plugins to install. If LWP is not defined, then the default LWP would be $LRP. (To set some sane defaults.) The packagename[:R|r|F|f] format would be supported. (Like the LRP= format) The LWP format is for plugins that don't need to save "state" or have configuration files. For plugins that need to save state, the LRP format can continue to be used. Since this extends the LEAF.CFG file format, and introduces a new extension (LWP), I'm interested in knowing if anyone has problems with this proposal. Thanks! ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
