Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Envelope-To: users@subversion.apache.org
Date: Sun, 16 Aug 2015 18:00:13 +0200
From: =?utf-8?Q?Thorsten_Sch=C3=B6ning?= <tschoening@am-soft.de>
Organization: AM-SoFT IT-Systeme
Message-ID: <1864338439.20150816180013@am-soft.de>
To: Subversion <users@subversion.apache.org>
Subject: Re: Error "mod_dav_svn close_stream: error closing write stream"
 using a write-through proxy
In-Reply-To: 
 <CAOCN9ry-vhS8KuSAJBYJ_cOmfHCyYyzbtLw=khS4KTK-TkeiSA@mail.gmail.com>
References: <1226955392.20150815161651@am-soft.de>
  <CAOCN9ryd0aGxjvMHrj-DXEcZnw8-ghN7au+xr+ahHEB3sDhvmQ@mail.gmail.com>
  <085857.20150816112118@am-soft.de>
  <CAOCN9ry-vhS8KuSAJBYJ_cOmfHCyYyzbtLw=khS4KTK-TkeiSA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Guten Tag Nico Kadel-Garcia,
am Sonntag, 16. August 2015 um 14:58 schrieben Sie:

> But you need an *authenticated* mirror, right? As opposed to a public mir=
ror?

Yes, some repos contain data of different customers and we don't want
them to see each other, which is currently working great with path
based authorization using authz files and mod_dav_svn is using the
same ones.

But looking at my problem I don't think authorization itself would
make any difference. Instead it seems that commits in general are
failing because of some incompatibility with my SSH tunnel. Which is
interesting because I successfully commit using svnserve over a SSH
tunnel for years now...

> ViewVC is my friend for pure visual web access, it's packaged for most
> distributions and is well maintained.

Sounds I need to have a second look, I had the impression there's not
much activity anymore as well. One important reason using WebSVN in the
past was that I found it to be far more beautiful with its default=20
templates already and somewhat easier to install. But ongoing
maintenance is a joker of course. :-)

> Ahh. Hmm. I'm not sure why it couldn't, if you can propagate the
> configurations for access among the different masters and slaves, and
> simply designate the slave servers with the svnserve *daemon's* user
> account having only read access to the relevant repositories.

From=20my understanding the important part about using master-slave with
mod_dav_svn is SVNMasterURI, so you have one endpoint for all users
and depending on what a user tries to do mod_dav_svn either serves
read only operations on its own or forwards write access to the
configured target. But all users always use the same entry point. I
don't see how this is possible using svnserve only, because it simply
lacks that forwarding logic to a master writable repo.

And that's what I want: All my customers should only access the same
public VM for their repos, regardless if they have write access or
not. If they get write access in the future, they don't need to change
anything, just commit and mod_dav_svn handles everything else. In
theory...

Mit freundlichen Gr=C3=BC=C3=9Fen,

Thorsten Sch=C3=B6ning

--=20
Thorsten Sch=C3=B6ning       E-Mail: Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Gesch=C3=A4ftsf=C3=BChrer: Andreas Muchow