On Mar 28, 2017, at 1:16 AM, Florian Balmer <florian.bal...@gmail.com> wrote:
>
> #!./fossil cgi fossil.config
That relies on behavior POSIX hasn’t specified:
https://stackoverflow.com/questions/4303128/
What’s wrong with doing it the portable way?
#!/bin/sh
exec ./fossil cgi fossil.config
I’ll grant that it’s slightly inefficient, but if you were worried about that,
you wouldn’t be using CGI, right?
But if you actually do care about efficiency, perhaps one of the efficient
methods of serving Fossil via HTTP would indirectly solve your current problem:
“fossil server” directly, “fossil server” behind an HTTP[S] proxy, and SCGI are
faster than plain old CGI.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
