Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

2017-02-14 Thread Thomas Bilk 
So I did bisect yesterday and oh wonder, everything worked properly. I
don't know why I had an issue on Sunday but today it works on a new
test server as well as on my production server. So all-clear for the
server --scgi command.

I would like to use the occasion to thank you developers of fossil
again for this magnificent piece of software. I have to use git at
work which is a mess and I am so happy that I can use a good source
control system for all my project. So, thank you again.

Best regards.
Thomas.

> 2017-02-13 0:28 GMT+01:00 Richard Hipp :
>>> I guess there was a regression introduced somewhere between [8b03934e]
>>> and [fb4b87d9].
>>
>> Would you be willing to bisect for us?
>
> Sure. I will report my findings later today.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

2017-02-13 Thread Thomas Bilk 
2017-02-13 0:28 GMT+01:00 Richard Hipp :
>> I guess there was a regression introduced somewhere between [8b03934e]
>> and [fb4b87d9].
>
> Would you be willing to bisect for us?

Sure. I will report my findings later today.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

2017-02-12 Thread Richard Hipp 
On 2/12/17, Thomas Bilk  wrote:
>
> I guess there was a regression introduced somewhere between [8b03934e]
> and [fb4b87d9].

Would you be willing to bisect for us?

-- 
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

[fossil-users] Fossil SCGI Server Regression (from 1.36 to 1.37)

2017-02-12 Thread Thomas Bilk 
Hi all.

I was finally upgrading my fossil server and encountered what I assume
to be a regression. I am using the fossil server with scgi behind an
nginx web server. I am hosting a directory with fossil repositories.
These is my configuration:

The fossil server is started with this
fossil server --localhost --scgi --port 12001 /var/repos

The nginx config:
server {
  listen80;
  location / {
include scgi_params;
scgi_pass   localhost:12001;
scgi_param  SCRIPT_NAME "";
  }
}

Until version 1.36 I could access my projects on from the “/var/repos”
folder like this: “http://myserver.com/myrepo”. When I upgraded my
fossil binary to version 1.37 [fb4b87d9] this does not seem to work
any more.

I got it to work partially by adding the “--baseurl
http://myserver.com/” parameter to the fossil call and configuring
nginx to use “scgi_param  PATH_NAME $fcgi_path_name;”. But that always
led to a redirect when I called the URL from above to
“http://myserver.com//myrepo/index” with an additional slash.

I guess there was a regression introduced somewhere between [8b03934e]
and [fb4b87d9]. I am currently sticking with the older version but
would love to upgrade.

Best regards,
Thomas.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users