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


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

2015-03-29 Thread Dewey Hylton
i have the following running to serve a directory full of fossil archives:
/usr/bin/fossil server --repolist --port 8181 /data/fossil

this appears to work perfectly when directly hitting the site:
http://fossil.server.local:8181/
http://fossil.server.local:8181/somefossil
http://fossil.server.local:8181/somefossil/wiki

i need this behind nginx so that is accessible via proxy. so i've added the 
following config to my nginx.conf:
server {
  listen 80 ;
  server_name fossil.server.local ;
  location / {
proxy_pass http://localhost:8181/ ;
proxy_set_header Host $host ;
  }
}

this also appears to work properly. BUT the fossil repo needs to live under 
/fossil on the main site. so i've changed the nginx.conf to look like this:
server {
  listen 80 ;
  server_name www.server.local ;
  location /fossil/ {
proxy_pass http://localhost:8181/ ;
proxy_set_header Host $host ;
  }
}

with this, the repolist works properly the links are relative so the browser 
gets directed to the fossil archive under /fossil/ ... 

however, each reference inside the rendered pages do not include /fossil/ so 
all links are broken and of course the theme does not show. for example, 
visiting this page:
http://www.server.local/fossil/somefossil/home
produces the following link (among others):
http://www.server.local/somefossil/wiki

so i change the fossil command line to this:
/usr/bin/fossil server --repolist --port 8181 
--baseurl=http://www.server.local/fossil /data/fossil

this causes similar breakage, only the generated reference is now missing the 
project name and looks like this:
http://www.server.local/fossil/wiki

so ... is there a way to accomplish this without using cgi? am i on the right 
track? what am i missing?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users