On Fri, Feb 05, 2010 at 04:40:06PM +0100, Olivier Berger wrote: > Package: gforge-web-apache2 > Severity: normal > > Hi. > > It's very hard to test only parts of fusionforge, or install it and adapt the > web configuration since every directives are assembled in one big and complex > config file. > > This should be improved, as discussed with maintainers. > > Just a placeholder to track comments/progress. > > Best regards, >
I think that the current /etc/gforge/httpd.conf, used as /etc/apache2/sites-enabled is just one example of what could be wished by the admin of a dedicated fusionforge system. But one may wish to use fusionforge in different contexts, where there are several other web apps on the same machine, and where fusionforge may not be available at '/' but somewhere below a particular path (for instance /fusionforge/). I think it would be better if the config file was just provided as an example, together with a minimal other apache app config file (for instance to be used as /etc/apache2/conf.d/fusionforge) that would provide only basic parts for a /fusionforge/ like installation. Any comments ? Best regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
