>> 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. I completely agree too. At the moment, i'm using 2 "fossil server" instances to serve to repositories on a Windows Home Server on two different ports. I added http://urlrewriter.codeplex.com/ to my IIS-configuration and using the following rules to rewrite the URLs like in apache. After switching two the new multi-repository-server, i've only to modify the replacements rules. In the same way, i could add a list-repository-page, just by adding a corresponding rule. RewriteRule ^/fossilscm$ fossilscm/index [QSA,NC,R] RewriteRule ^/fossilscm(/?.*)$ http://<servername>:8001$1 [QSA,NC,P] RewriteRule ^/fossil$ fossil/index [QSA,NC,R] RewriteRule ^/fossil(/?.*)$ http://<servername>:8000$1 [QSA,NC,P] So i call http://<servername>/wiki And get http://<servername>:8000 Where my fossil repo lives :-) In the future, the rule 2 would be changed to RewriteRule ^/fossilscm(/?.*)$ http://<servername>:8000/fossilscm/$1 [QSA,NC,P] Many Thanks Wolfgang _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
