To be fair, I'm being glib - it probably works fine if properly configured, but configuring CGI plugins on IIS is not a straightforward task. I tinkered with it for an afternoon and only got so far as IIS loading an instance of fossil.exe for each inbound request. Sadly, the .exes would just sit there chewing up 13% of my CPU (each) and never return, causing the browser to timeout. After a dozen requests, the machine would tank because of all the stalled (but active) fossil processes... not pretty, and hard to debug since i couldn't "see" what the fossil.exes were up to.
"fossil server" took all of 3 minutes to get running. All I had to do was open up all the right ports in my firewalls and tell NSSM to run it as a service. Done. On Tue, Jul 19, 2011 at 7:05 AM, Jeremy Anderson <[email protected]> wrote: > Unless you're on windows+IIS. Then it takes hours. And maybe then it > doesn't even work... :) > > On Tue, Jul 19, 2011 at 6:06 AM, Stephan Beal <[email protected]>wrote: > >> On Tue, Jul 19, 2011 at 11:35 AM, Richard Hipp <[email protected]> wrote: >> >>> (2) The "fossil ui" and "fossil serve" commands are easier to use and >>> provide much more information than the "hg serve" command. >>> >> >> Let's not forget: >> >> (2.5) The ability to run Fossil over a CGI. >> >> This has been THE killer feature for me the past several years. i've tried >> several times to get git running over cgi but never succeeded. In Fossil it >> takes all of 3 minutes. >> >> -- >> ----- stephan beal >> http://wanderinghorse.net/home/stephan/ >> >> _______________________________________________ >> 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
