I operate in an environment without CGI support (We run an Nginx web server, which doesn't support CGI). Implementing Fossil using a bunch of it's own servers behind Nginx as a proxy is undesirable for a multitude of reasons: It means configuring a Fossil service for every repository, which means I end up with a mass of ports owned by Fossil to manage, I have to configure all the services to start [or run them from xinetd], and that you need a subdomain for each proxied repository. Nginx does excel, however, at FastCGI.
I was wondering: 1) How modularized is the Fossil web HTTP support? I'd imagine it is quite heavily, considering that it supports both running it's own server and CGI. 2) How hard would it be to modify it to support FastCGI? 3) How does Fossil parallelize requests? Thanks, Owen _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
