Got it!!!
I created a virtual directory that redirects all requests to a Perl script that takes CGI requests like this: http://myserver/Fossil/Projects/.../project.fossil generates a Fossil CGI script (Fossil.cgi): #!\Program Files\Fossil\Fossil repository: \Projects\...\myrepository.fossil then invokes Fossil: Fossil \...\Fossil.cgi Fossil returns HTML containing references to resources in the repository like this: <img src="/Fossil/.../myrepository.fossil/logo" alt="logo" /> The browser requests each resource as: http://myserver/Fossil/.../myrepository.fossil/logo The Perl script parses each resource request into repository name and the resource (ex. /logo), recreates the Fossil.cgi, sets the CGI environmental variables then invokes Fossil: PATH_INFO=/logo Whew! Tony Perovic Compumation, Inc. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Lluís Batlle i Rossell Sent: Friday, March 04, 2011 4:45 PM To: [email protected] Subject: Re: [fossil-users] Fossil on IIS On Fri, Mar 04, 2011 at 04:27:44PM -0600, Tony Perovic wrote: > Q: How should the CGI script invoke Fossil to request these internal > resources? The CGI is quite a defined interface, telling any query information through environment variables, and expecting any answer in stdout. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
