On Tue, Mar 4, 2014 at 10:27 PM, Jon <jon.for...@gmail.com> wrote:
> Thank you. Your setup is fastcgi, not scgi, correct?
>
> I'm now unclear about the scgi setup. From the wiki I thought scgi
> requires just two pieces. First, start fossil like
>
> fossil --localhost --scgi /srv/fossils/partner
>
> and second, set an nginx location similar to
>
> location ~ ^/partner/ {
> include scgi_params;
> scgi_pass 127.0.0.1:8080;
> scgi_param SCRIPT_NAME "/partner";
> }
>
> A stub cgi script is not needed.
>
> I'll tinker with scgi tomorrow, but even if I get it working, I don't yet
> see how scgi ensures fossil generates correct links to it's gui while that
> route back user url's similar to
>
> http://somewhere.mydomain.com/partner/<repo-name>/...
>
> back to the fossil server listening to sgci protocol traffic
> on127.0.0.1:8080. With scgi I think I still need to configure nginx
> `location` trickery to handle uri and :80 to 127.0.0.1:8080 issues.
>
> Feels like I'm missing a piece of the puzzle and overcomplicating nginx +
> fossil.
>
>
I've only used nginx once, and that was to test the SCGI code of Fossil
when I was writing it. I didn't have to do anything special, other than
setting the SCRIPT_NAME scgi_param. The links that the GUI generates are
either relative, or else they are use the HTTP_HOST scgi_param, depending
on context.
http://www.fossil-scm.org/fossil/doc/tip/www/server.wiki#scgi shows my
complete setup. It just works. Don't try to over-think it.
--
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
