Hi Jeremy On Wed, May 27, 2009 at 11:19:28AM +0200, Jérémy Lal wrote: > I may have a plan : > - drop support for db configuration, since dbconfig-common do it as well if > not better
I agree. I do not want to break things that are working though. > - 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. That would be nice, yes. However different webservers have different capabilities, which must be decided by the package maintainer. > 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] This should really be configured by the admin. A default could be considered but based on my experience this is very hard to do in a common way. > - alias for common static files provided by some debian packages (images, > css, javascript) Yes, and the problem again is that we need to be able to consider virtual hosts in a way that works for most installations. > - a simple cgi Not sure what you mean here. As far as I know you just place things in the cgi dir and you are done. > - a fastcgi backend (possibly using spawn-fcgi instead of relying on the > web server for spawning). Now we are rather far from configuration. This is something completely different. > it would be very different from the current wwwconfig, so i guess breaking > compatibility > is inevitable. Agree. As you can see from my answers on bug reports lately (the last years actually) I do not use wwwconfig-common myself, but I still maintain it because other package maintainers find it useful. > any comments on this ? I suggest you create a new package and convince package maintainers to switch to your version. I think the easiest way is to take a few packages that currently use wwwconfig-common, see what they are using it for and then create a software that do this better than wwwconfig-common. I do not think it is very hard as I hacked this package because I wanted something common for the horde2 and imp3 packages at that time. Nowdays I have decided to drop all automatic configuration support in horde as I got so many complaints on it from bug reports. Do not work in sitation A, not compliant with this Debian rule and so on. Best regards, // Ola > Regards, > Jérémy Lal. > > > > -- --------------------- Ola Lundqvist --------------------------- / [email protected] Annebergsslingan 37 \ | [email protected] 654 65 KARLSTAD | | http://inguza.com/ +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
