On Tue, Aug 13, 2013 at 1:19 PM, Natacha Porté <nata...@instinctive.eu>wrote:
> > I'm afraid I'm missing something in this FastCGI discussion starting > from this post. What is the benefit of using FastCGI instead of > (existing) HTTP between nginx and a long-lived fossil process? > Or instead of HTTP between nginx and a inetd-spawned one-shot fossil > process? > > FastCGI is useful mainly because nginx doesn't support CGI. Yes, you can work around this by using nginx as a reverse proxy, but that requires a lot of nginx configuration knowledge. I have SCGI working on my local check-out now, for unix. I'm working on getting SCGI working on windows too. As soon as the whoe thing is finished, I'll check it in, together with documentation on how to configure nginx to use it. That should make using Fossil with nginx a little easier. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
