On 09/03/16 16:44, Niemann, Hartmut wrote:
Hi!
I learned that finer-as-per-repository-grained read access is rather
"expensive" in terms of server load
because rights have to be checked for each file updated.
So it would be best that you have separate repositories for separate "read"
user gr
Hi!
I learned that finer-as-per-repository-grained read access is rather
"expensive" in terms of server load
because rights have to be checked for each file updated.
So it would be best that you have separate repositories for separate "read"
user groups.
I have not heared about somebody who use
hi everybody,
I realize this certainly is somewhere in books but I'm
hoping few experts would not mind sharing their
thoughts/recommendations on how to...
set up svn structure where interface to it is only http and
flexibility + ability to finely grain user access is the key
obje
Hello,
I am running Subversion 1.7.7 on Ubuntu 12.04 using apache2 + dav_svn +
mod-auth-ntlm-winbind for authentication. In my apache config, I specify an
authz file for access control:
AuthzSVNAccessFile /path/to/authz
In the repository, I have several different sub-directories:
/trunk/a
/t
Downloaded subversion edge to run on my current server serving svn 1.5.x with
apache and repo's accessed via HTTP
figured i use subversion edge to get the latest svn server - 1.7.1 as i could
not find just the binaries to replace over my existing installation.
in my 1.5.x i had this in my apach
> > From: "Cooke, Mark"
> > To: j s ; "users@subversion.apache.org"
> >
> > Sent: Tuesday, November 15, 2011 10:05 AM
> > Subject: RE: user access
> >
> > [We normally bottom-post on this list to make it easier to
> > re
From: "Cooke, Mark"
To: j s
Sent: Tuesday, November 15, 2011 10:36 AM
Subject: RE: user access
> From: "Cooke, Mark"
> To: j s ; "users@subversion.apache.org"
>
> Sent: Tuesday, November 15, 2011 10:05 AM
&g
From: "Cooke, Mark"
To: j s ; "users@subversion.apache.org"
Sent: Tuesday, November 15, 2011 10:05 AM
Subject: RE: user access
[We normally bottom-post on this list to make it easier to read in order... See
in-line below]
>
From: "Cooke, Mark"
To: j s ; "users@subversion.apache.org"
Sent: Tuesday, November 15, 2011 10:05 AM
Subject: RE: user access
[We normally bottom-post on this list to make it easier to read in order... See
in-line below]
>
[We normally bottom-post on this list to make it easier to read in order... See
in-line below]
> > -Original Message-
> > From: j s [mailto:jbluede...@yahoo.com]
> > Sent: 15 November 2011 13:29
> > To: users@subversion.apache.org
> > Subject: user acces
e.
appreciate any useful tips.
From: "Cooke, Mark"
To: j s ; "users@subversion.apache.org"
Sent: Tuesday, November 15, 2011 8:51 AM
Subject: RE: user access
> -Original Message-
> From: j s [mailto:jbluede...@yahoo.com]
> Sent: 15 November 2011 13:
> -Original Message-
> From: j s [mailto:jbluede...@yahoo.com]
> Sent: 15 November 2011 13:29
> To: users@subversion.apache.org
> Subject: user access
>
> Have svn running on windows/apache and currently dev team
> accesses svn repo's using http and tor
Have svn running on windows/apache and currently dev team accesses svn repo's
using http and tortoisesvn
They access the repos using their domain credentials set up in apache config.
we now have a group of temps that we want to create a new repo for and that
they should only access that repo ei
13 matches
Mail list logo
