> (3) Configure nginx to relay requests to the "fossil server" instance.
Afaik, this only works if the root is relayed, not if the fossil server instance is rooted at a base path. For example, forwarding http://www.domain.com/ to a fossil server would work, but forwarding http://www.domain.com/path/to/ would not work, because the generated html would not have correct href's (it would not have the '/path/to' bit). I've posted a patch to make this work july 11th, 2010, but I don't think it was accepted into the main code. Paul On 25 Sep 2011, at 18:53 , Richard Hipp wrote: > > > On Sun, Sep 25, 2011 at 12:25 PM, i <i...@ijser.cn> wrote: > in fact , I want to make several repositories use one port, and under nginx. > or with CGI anyway.. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > (1) Put all of your Fossil repositories in the same directory. For example > /home/www/repos. Name each with the ".fossil" suffix. So, for example, you > might have /home/www/repos/aaa.fossil, /home/www/repos/bbb.fossil, > /home/www/repos/ccc.fossil, and so forth. > > (2) Run "fossil server /home/www/repos". By giving it a directory as an > argument, it will serve any fossil repository under that directory, using the > base name of the repository as the prefix on the URL. Example: > http://localhost:8080/aaa/timeline, http://localhost:8080/bbb/timeline, etc. > > (3) Configure nginx to relay requests to the "fossil server" instance. > > > -- > 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 mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
