On Sat, Sep 10, 2016 at 10:44:34AM +0100, Zombies wrote: > On 10 September 2016 at 01:52, Francis Daly <fran...@daoine.org> wrote: > On Fri, Sep 09, 2016 at 08:27:53AM +0100, Zombies wrote:
Hi there, Good that you got it working. > > > ./fossil server --baseurl "https://fossil.mydomain.com:443/" > > repos/myRepo > > > > "baseurl" must start with "http://" or "https://" (enforced in code), > > and must not end in "/" (not enforced directly). It is good when you > > It seems to enforce an ending '"/", > If I try and use it without the ending '/' - it doesnt seem to like it at > all:- > > ./fossil server --baseurl "https://fossil.mydomain.com:443" repos/myRepo > argument to --baseurl should be 'http://host/path' or 'https://host/path' Yes - it's a bit of a terminology confusion, but: the "/path" part is required (or the option is not accepted) *and* the "/path" must not end in "/" (or the double-slashes produced cause the output to break). So if you want your "repos/myRepo" as served by fossil, to appear to be at "/base/myrepos/myRepo" when served by the public-facing web server that hides fossil, then you would use "--baseurl http://whatever/base". The one (common?) case where --baseurl does not work, is exactly your case: the public-facing web server just handles https but otherwise does not change the url. If you were using something like stunnel for https and spawning a new "fossil" for each incoming request, you could use "fossil http --https" But that is not available for "fossil server". As it happens, it does not matter that "--https" and "--baseurl" do not work in this case, because just setting the env-var does work. Cheers, f -- Francis Daly fran...@daoine.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users