I may have a plan : - drop support for db configuration, since dbconfig-common do it as well if not better - add support for many web servers, if not all that are in debian. The idea would be to choose on which already installed web server the user wants configuration to be done.
to add that support, we should first list use cases for httpd configurations, here are the configurations i can list based on my own experience : - URL for accessing the web app : schema://host[:port][/path] - alias for common static files provided by some debian packages (images, css, javascript) - a simple cgi - a fastcgi backend (possibly using spawn-fcgi instead of relying on the web server for spawning). it would be very different from the current wwwconfig, so i guess breaking compatibility is inevitable. any comments on this ? Regards, Jérémy Lal. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
