On Nov 9, 2009, at 8:11 AM, Franz wrote:

> Hello,
>
> this is my first post on this list so please bear with me! ;-)
>
> I want to set up a central fossil server in our company network. So
> I've created a local repository on my desktop machine, worked there
> for some time and decided it was time to make it "public".
>
> Like it is recommended in the fossil quick start documentation I
> started the fossil server on my desktop and cloned ("fossil clone...")
> the repository on the server.
>
> Setting up the cgi server worked as expected so that I was able to
> browse to the server repository.
>
> We are behind a proxy server but the access to the fossil server
> should bypass the proxy to work.
>
> When I make changes on my local repository and commit it says
> "Autosync: " with the correct server URL.

Do you get a line that says "via proxy: ..."?

> But on the server I can find
> no changes. I tried disabling the proxy with "setting proxy off" to no
> avail. Also the command line option "--proxy off" doesn't help either.
>
> So i tried on the server a "fossil pull.." which did only work with
> the cli option "--proxy off".

The proxy settings are only relevant on the client.  Servers having  
nothing to do with proxies and ignore proxy settings.

>
> So here my questions:
>
> * I would like for autosync to work but I can't see how to do this
> with proxy. Do I have to unset proxy on the client and server? Should
> I write a wrapper script for fossil that temporarily unsets the proxy
> environment variable?

If you have an "http_proxy" environment variable set, or if you have  
"fossil setting proxy" set to a proxy, then you can disable the proxy  
for autosync using the "--proxy off" command-line argument when you  
update or commit.

>
> * In the quick start docs it says that
>
> "The fossil setting for the HTTP proxy takes precedence over the
> environment variable and the command-line option overrides both."
>
> But it seems  that the proxy environment settings take precedence over
> the fossil setting. Is this wrong in the docs?

I just retested this.  It appears to work as described in the  
documentation for me.  Can you send me a specific test case which is  
not working?

D. Richard Hipp
[email protected]



_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to