Re: File access control

2011-10-02 Thread Thorsten Schöning
Guten Tag Grant, am Sonntag, 2. Oktober 2011 um 03:07 schrieben Sie: > All of the big enterprise websites allow each of their developers to > check out a full working copy of the company code with only an NDA/NCC > to protect them? Mostly, yes and why do you think this is not enough? > It would

Re: File access control

2011-10-01 Thread Andreas Krey
On Sat, 01 Oct 2011 18:07:29 +, Grant wrote: ... > Ouch. If testing is done on the developer's local machine, he will > need a full working copy and it will be impossible to restrict read > access to one or a few files as I had planned to do with path-based > authz. Instead, could I check out

Re: File access control

2011-10-01 Thread David Chapman
On 10/1/2011 8:26 PM, Grant wrote: Ouch. If testing is done on the developer's local machine, he will need a full working copy and it will be impossible to restrict read access to one or a few files as I had planned to do with path-based authz. Instead, could I check out a working copy of the rep

Re: File access control

2011-10-01 Thread Grant
>> Ouch. If testing is done on the developer's local machine, he will need a >> full working copy and it will be impossible to restrict read access to one >> or a few files as I had planned to do with path-based authz. Instead, could >> I check out a working copy of the repository to a staging mach

Re: File access control

2011-10-01 Thread David Chapman
On 10/1/2011 6:07 PM, Grant wrote: Ouch. If testing is done on the developer's local machine, he will need a full working copy and it will be impossible to restrict read access to one or a few files as I had planned to do with path-based authz. Instead, could I check out a working copy of the r

Re: File access control

2011-10-01 Thread Ryan Schmidt
On Oct 1, 2011, at 20:07, Grant wrote: >> There is a repository -- a database -- that holds your code. The current >> version and all past versions, including, if you like, branches. This could >> be on any server you like -- the production server, the development server, >> a completely separ

Re: File access control

2011-10-01 Thread Grant
> Again I strongly encourage you to spend time reading the book. The first > several chapters should solidify for you how people work with Subversion. > There's no sense in us explaining it all here on the list when writers have > already spent years refining the words in the book. But I'll try

Re: File access control

2011-10-01 Thread Les Mikesell
On Sat, Oct 1, 2011 at 6:15 PM, Grant wrote: > > Would I need to install subversion on the production machine, or would > the subversion server running on the dev machine just treat the > production machine as a target destination and use SSH to transfer the > files? How you move things around is

Re: File access control

2011-10-01 Thread Ryan Schmidt
On Oct 1, 2011, at 18:15, Grant wrote: > Would I need to install subversion on the production machine, or would > the subversion server running on the dev machine just treat the > production machine as a target destination and use SSH to transfer the > files? > So I'll be OK if I commit changes

Re: File access control

2011-10-01 Thread Grant
>> After committing changes to the repository on the dev machine, could I >> use svn update instead of rsync to bring the production machine's >> files in sync with those on the dev machine? > > Yes, and even better if you have an intermediate staging/testing > space, but that may be overkill for s

Re: File access control

2011-09-30 Thread Chris Albertson
On Fri, Sep 30, 2011 at 7:16 PM, Grant wrote: > Is it risky because I would be using rsync instead of svn update, or > is it risky because I wouldn't be using a test/staging machine?  Why > can't testing be done on the dev machine? risky because you can't 100% prove what you got is exactly what

Re: File access control

2011-09-30 Thread Les Mikesell
On Fri, Sep 30, 2011 at 9:16 PM, Grant wrote: >> Normally you would do that with a subversion client, creating >> different workspaces for development, testing, and production with >> commit/update operations to move data instead of rsync.   Variations > > After committing changes to the repositor

Re: File access control

2011-09-30 Thread Grant
>> My workflow above only describes a single repository on the dev >> machine, the production machine wouldn't have a repository.  rsync >> would synchronize the source files, not the repository. >> > > Normally you would do that with a subversion client, creating > different workspaces for develop

Re: File access control

2011-09-30 Thread Les Mikesell
On Fri, Sep 30, 2011 at 8:46 PM, Grant wrote: > > My workflow above only describes a single repository on the dev > machine, the production machine wouldn't have a repository.  rsync > would synchronize the source files, not the repository. > Normally you would do that with a subversion client, c

Re: File access control

2011-09-30 Thread Grant
>> Right now I'm trying to decide whether or not I should use subversion. >>  Hopefully there is a less time-consuming method for making that >> determination. >> >> My goals are to implement a good development framework and to define a >> (changing) list of files which are the only files a develop

Re: File access control

2011-09-30 Thread Les Mikesell
On Fri, Sep 30, 2011 at 8:16 PM, Grant wrote: > > Right now I'm trying to decide whether or not I should use subversion. >  Hopefully there is a less time-consuming method for making that > determination. > > My goals are to implement a good development framework and to define a > (changing) list

Re: File access control

2011-09-30 Thread Grant
>> That's great news.  I've never used a version control system or any >> sort of developer framework.  Would something like this work? > > I'm sorry but it really does sound like you have no idea how Subversion > works. Please spend several days reading the book front to back: > > http://svnbook.

Re: File access control

2011-09-30 Thread Ryan Schmidt
On Sep 30, 2011, at 18:37, Grant wrote: > That's great news. I've never used a version control system or any > sort of developer framework. Would something like this work? I'm sorry but it really does sound like you have no idea how Subversion works. Please spend several days reading the book

Re: File access control

2011-09-30 Thread Grant
>> I see that subversion supports path-based authorization: >> >> http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html >> >> Is there a way to do file-based authorization?  Or maybe some sort of >> trickery to mimic file-based authorization?  If not, can anyone think >> of a way

Re: File access control

2011-09-29 Thread Ryan Schmidt
On Sep 29, 2011, at 10:02, Thorsten Schöning wrote: > I didn't try, but if it works it would be nice to get that mentioned > in the book. I always thought directories are all which is possible. You should submit that feedback to the people who write the book. They have a separate mailing list.

Re: File access control

2011-09-29 Thread Thorsten Schöning
Guten Tag Mark Phippard, am Donnerstag, 29. September 2011 um 14:37 schrieben Sie: > Files are paths too. The path-based authz applies to any path (folder > or file). For example: > [repos:/trunk/readme.txt] > @releng = rw > * = r > A rule like that works fine. I didn't try, but if it works i

Re: File access control

2011-09-29 Thread Ian Wild
On Thu, Sep 29, 2011 at 1:34 PM, Prabhu Gnana Sundar wrote: > ** > On Thursday 29 September 2011 05:10 PM, Ian Wild wrote: > > WANdisco offer a commercial product which does exactly this based on our > proxy technology. > > http://www.wandisco.com/subversion/accesscontrol has more details - feel

Re: File access control

2011-09-29 Thread Mark Phippard
On Wed, Sep 28, 2011 at 10:41 PM, Grant wrote: > I see that subversion supports path-based authorization: > > http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html > > Is there a way to do file-based authorization?  Or maybe some sort of > trickery to mimic file-based authorizati

Re: File access control

2011-09-29 Thread Prabhu Gnana Sundar
On Thursday 29 September 2011 05:10 PM, Ian Wild wrote: On Thu, Sep 29, 2011 at 3:41 AM, Grant > wrote: I see that subversion supports path-based authorization: http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html Is there a way to do

Re: File access control

2011-09-29 Thread Ian Wild
On Thu, Sep 29, 2011 at 3:41 AM, Grant wrote: > I see that subversion supports path-based authorization: > > http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html > > Is there a way to do file-based authorization? Hi Grant, WANdisco offer a commercial product which does exact

Re: File access control

2011-09-29 Thread Thorsten Schöning
Guten Tag Grant, am Donnerstag, 29. September 2011 um 04:41 schrieben Sie: > Is there a way to do file-based authorization? Not that I read of. > Or maybe some sort of > trickery to mimic file-based authorization? You can always create folders, depending on what exactly you have to protect agai

RE: File access control

2011-09-28 Thread Cooke, Mark
> -Original Message- > From: Grant [mailto:emailgr...@gmail.com] > Sent: 29 September 2011 03:42 > To: users@subversion.apache.org > Subject: File access control > > I see that subversion supports path-based authorization: > > http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbased