> If Fossil returns the index.html file, then before long you also want > to return various images and CSS files that index.html references. > And then people will want a way to return favicon.ico. And > robots.txt. And then you will need a way to customize the mimetypes > of the various files. Already here is a feature request to allow the > repositories to have extensions other than ".fossil". How long before > people want the ability to handle multiple domains using the HTTP_HOST > property of the HTTP header? > > I do *not* want to turn Fossil into a general-purpose web server and > replacement for Apache. That is not its purpose. We have to draw the > line somewhere, and I propose to draw the line here.
I completely agree. Stick to your knitting, as they say. Maybe someone who has need for this type of setup could write a quick tutorial on getting something like lighthttpd or something equally light weight and self-contained set up for local use. With 2 line apache CGI setup, I'm not sure how much easier it could get if you really need to run on a normal server. S _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
