I've resolved this. I'll share my outcome for future folks who want to get
a low-maintenance fossil HTTPS server up quickly.
The initial scheme was to use 'stunnel' as a reverse proxy to terminate
SSL, and forward the request on to the fossil web server daemon that is
listening on the same box.
What happens if you set base_url without trailing slash? e.g.
https://foobar.com:10443;
On Wed, Jul 24, 2013 at 4:55 PM, Eric Rubin-Smith eas@gmail.com wrote:
I think the point here is that with a baseurl of
https://foobar.com:10443/;, certain links exposed by the fossil HTML
I've started a fossil repo by importing a git repo to my local laptop, and
then cloning the repo over to my target production web server.
For testing, I've exposed the fossil server like this:
/usr/local/bin/fossil server /home/fossil/myrepo.fossil --th-trace -P 10080
--baseurl
Thus said Eric Rubin-Smith on Tue, 23 Jul 2013 22:02:11 -0400:
/usr/local/bin/fossil server /home/fossil/myrepo.fossil --th-trace -P 10080
--baseurl http://localhost:10080/
Try removing the --baseurl option.
It works for me when I do:
fossil server /tmp/test.fossil
ssh -L
Thus said Andy Bradford on 23 Jul 2013 20:22:37 -0600:
fossil server /tmp/test.fossil
Of course I meant:
fossil server -P 10080 /tmp/test.fossil
ssh -L 10080:localhost:10080 remote
Cheers,
Andy
--
TAI64 timestamp: 400051ef3c17
___
Yes, that works for the test case. But I think I'll need --baseurl for
when I put fossil behind an SSL-terminating reverse proxy and want to
access it using the company FQDN.
On Tue, Jul 23, 2013 at 10:22 PM, Andy Bradford
amb-sendok-1377224557.emjjjkijcgiknbipb...@bradfords.org wrote:
Thus
6 matches
Mail list logo
