Re: [fossil-users] using fossil server --repolist behind nginx proxy

2015-04-01 Thread Dewey Hylton 
 From: Andy Bradford 
 amb-sendok-1430461727.niogihkppihojgmic...@bradfords.org
 To: Dewey Hylton dewey.hyl...@gmail.com
 Cc: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
 Sent: Wednesday, April 1, 2015 2:28:46 AM
 Subject: Re: [fossil-users] using fossil server --repolist behind nginx 
 proxy
 
 I believe --baseurl  is what you actually want to  use, however, I'm not
 sure --baseurl even works. Everytime I've seen someone try to use it, it
 never seems  to work right.  Is there  anyone successfully using  it? So
 it's possible that --baseurl  has a bug in that when it  is set, it does
 not append  the name  of the  actual repository  once the  repository is
 known.
 
 Please try the following:
 
 http://www.fossil-scm.org/index.html/info/7c8eb85c24ab99ed
 
 Thanks,
 
 Andy
 --
 TAI64 timestamp: 4000551b9041

thanks, andy! this appears to work as it should. in case someone else ever 
searches
the list for this (i find it hard to believe i'm the only one wanting to use 
this
functionality), i'll include both fossil and nginx configurations below.

meanwhile, should we expect this change to be committed to trunk and available 
in
the next version?


fossil command:
/usr/local/bin/fossil server \
--repolist \
--port 8181 \
--baseurl=http://www.server.local/fossil \
/data/fossil


nginx cfg block:
server {
  listen 80 ;
  server_name www.server.local ;
  location ^~ /fossil/ {
proxy_pass http://localhost:8181/ ;
proxy_set_header Host $host ;
}
}

in fact, it appears as if the Host header doesn't actually need to be set for 
this to work properly.

thanks again, andy, for stepping up to the plate and doing this!
___
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] using fossil server --repolist behind nginx proxy

2015-04-01 Thread Andy Bradford 
Thus said Dewey Hylton on Wed, 01 Apr 2015 13:13:23 -0400:

 meanwhile, should we  expect this change to be committed  to trunk and
 available in the next version?

It looks  like it has  already been merged. I  might still add  an extra
condition to  be sure this  is only used when  the repository name  is a
directory of  repositories to serve  as an extra precaution  to preserve
original behavior for single file servers.

Thanks,

Andy
--
TAI64 timestamp: 4000551c4e4a
___
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] using fossil server --repolist behind nginx proxy

2015-03-31 Thread Dewey Hylton 
 From: Dewey Hylton dewey.hyl...@gmail.com
 To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
 Sent: Sunday, March 29, 2015 11:07:31 AM
 Subject: Re: [fossil-users] using fossil server --repolist behind nginx 
 proxy
 
  From: David Macek david.mace...@gmail.com
  Sent: Sunday, March 29, 2015 10:56:07 AM
  
  On 29. 3. 2015 16:55, Andy Bradford wrote:
   Given  that you're  using nginx  as  a proxy,  perhaps you  need to  add
   --baseurl to the fossil server options?
  
  OP mentioned that he tried it.
 
 yeah ... that feature seems to be relevant only when one is *not* serving a
 directory. at least that's what my testing has shown.
 
 and for what it's worth, i'm working with:
 $ fossil version
 This is fossil version 1.32 [6c40678e91] 2015-03-14 13:20:34 UTC

... any other suggestions? i really prefer to stay away from cgi and making my 
own index page ...
___
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] using fossil server --repolist behind nginx proxy

2015-03-29 Thread Andy Bradford 
Thus said Dewey Hylton on Sun, 29 Mar 2015 10:03:29 -0400:

 so ... is  there a way to  accomplish this without using cgi?  am i on
 the right track? what am i missing?

Given  that you're  using nginx  as  a proxy,  perhaps you  need to  add
--baseurl to the fossil server options?

Andyk
-- 
TAI64 timestamp: 40005518126b


___
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] using fossil server --repolist behind nginx proxy

2015-03-29 Thread Dewey Hylton 
 From: David Macek david.mace...@gmail.com
 Sent: Sunday, March 29, 2015 10:56:07 AM
 
 On 29. 3. 2015 16:55, Andy Bradford wrote:
  Given  that you're  using nginx  as  a proxy,  perhaps you  need to  add
  --baseurl to the fossil server options?
 
 OP mentioned that he tried it.

yeah ... that feature seems to be relevant only when one is *not* serving a 
directory. at least that's what my testing has shown. 

and for what it's worth, i'm working with:
$ fossil version
This is fossil version 1.32 [6c40678e91] 2015-03-14 13:20:34 UTC
___
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] using fossil server --repolist behind nginx proxy

2015-03-29 Thread David Macek 
On 29. 3. 2015 16:55, Andy Bradford wrote:
 Given  that you're  using nginx  as  a proxy,  perhaps you  need to  add
 --baseurl to the fossil server options?

OP mentioned that he tried it.

-- 
David Macek



smime.p7s
Description: S/MIME Cryptographic Signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users