> OK. Well, the other thing you can do is lobby the nginx people to start > supporting CGI. :-)
I'm not a nginx user, and such would not work if the front web server and the fossil server are on different machines, as they are in my case. With the current fossil code base my workaround is to run a tiny webserver on the fossil machine that calls fossil in CGI mode and sets the SCRIPT_NAME environment variable appropriately based on the forwarded http header info. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
