On Wed, Apr 7, 2010 at 1:04 AM, Joshua Paine <jos...@letterblock.com> wrote:
> You do not have to hard-code the server name so long as its the same as > the fossil repo is being served through. Just linking to "/foo/bar" > means "http://whatever-domain-we-are-on-now.com/foo/bar";. It's the / at > the beginning that does that--just like a *nix filesystem path: `cd foo` > changes to 'working_directory/foo', but `cd /foo` changes to /foo. > i tried that, but in CGI mode my index.cgi _is_ my root dir (as far as Fossil CGI is concerned). My setup is: Apache on 3rd-party hoster: http://fossil.wanderinghorse.net under /repos/XXXX i have 12 or 15 repositories, each set up like: repos/REPONAME/index.cgi If i visit http://..../repo/Project, apache redirects me to /.../Project/index.cgi, and that ends up being the top path for any absolute OR relative links i add in Fossil (strangely enough, but i think that actually makes an iota of sense for most CGI apps). Locally i don't use CGI, but use "fossil ui" instead (much more convenient), which of course is rooted in the repo. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
