no kidding...
of course if you're going to allow the user to have a access layer that fits
on top of SVn, then you wouldn't have to allow access to the SVN repository.
but if you do this, then you're also going to have to replace/build the
access control mechanism.. which is ok if you're doing a workflow app..
the issue you run into is that you then restrict the user to only accessing
the files in your system via the website.. you pretty much disallow SVN
client apps.. which is why you'd have to deal with the svn user file access
file if you're going to allow a user to access the underlying files via the
web app, as well as the svn client app...
in your case, i imagine that you're only going to allow access via your web
app...
have you guys started development on your app? will it be open, or just for
your dev environment..
-bruce
-----Original Message-----
From: jason@subversus.org [mailto:jason@subversus.org]
Sent: Monday, June 19, 2006 7:36 AM
To: bedouglas@earthlink.net; users@subversion.tigris.org
Subject: RE: User File Access from Mysql DB...
If you have a higher level interface to Subversion, then you wouldn't give
direct access to the Subversion repository. Instead, I would imagine that
the higher level interface would intercept all of the permission issues and
handle them elsewhere (probably in a database of some sort). I would only
use Subversion to handle the storage of the documents.
If you want to give direct access to the Subversion repository (through the
svn client or something like ToroiseSVN) then your problem becomes
exponentially tricky (because you would have to handle permission changes
somehow within Subversion... not recommended). But in the scenario I
present, no one uses Subversion directly... the interface would handle all
interaction with Subversion as a back-end.
-----Original Message-----
From: bruce [mailto:bedouglas@earthlink.net]
Sent: Monday, June 19, 2006 10:14 AM
To: jason@subversus.org; users@subversion.tigris.org
Subject: RE: User File Access from Mysql DB...
jason...
does your app allow for users to request that they be added to a given
area/part of the workflow...
how will you deal with users who want to dynamically change the folders of
the workflow that they have access to.
example:
foo.txt is placed in dev folder
sue wants access to the development folder (foo.txt)
bob wants access to the testing folder (foo.txt)
sue modifies foo.txt, and moves it to testing
bob completes testing of foo.txt and moves file
to production
the app should now delete/remove sue/bob from
the user file access file...
does the subversion API allow you to more or less intercept/redirect the
user file access process...
-bruce
-----Original Message-----
From: jason@subversus.org [mailto:jason@subversus.org]
Sent: Monday, June 19, 2006 6:42 AM
To: bedouglas@earthlink.net; users@subversion.tigris.org
Subject: RE: User File Access from Mysql DB...
While your example is kind of vague, it sounds like you need to utilize the
API to Subversion and possibly have a MySQL database back end. Such an
example would be an application (possibly web-based?) that acts as an
interface to Subversion (in which the files would be stored) and the
work-flow data stored in some form of a database.
I'm currently implementing a similar type of system... a document management
/ approval system that is based on top of Subversion / SQL Server. The
documents are uploaded and stored in Subversion, the document settings and
data are stored in SQL Server. The interface is a web application in which
individuals can view and approve the documents based on permissions.
-----Original Message-----
From: bruce [mailto:bedouglas@earthlink.net]
Sent: Monday, June 19, 2006 9:25 AM
To: users@subversion.tigris.org
Subject: User File Access from Mysql DB...
hi...
i'm considering Subversion as a reopistory, but i need the ability to
implement the SVN system in a workflow kind of application. this requires
that as a file goes from one part of the process to another, the user
assigned to that part of the process will have access to only the files in
that part of the process...
i also need to accommodate the fact that users can/might be switched to
different parts of the process.
i've considered keeping all this information in a mysql db, and then somehow
writing out the subversion user access file whenever a change is made to the
overall access system... this seems to be a good chunk of development, and
i'm not sure if it's the right thing to do..
i've also considered the possibility of having to rewrite subversion to have
it get the user file access rights information from a database.. but i'm not
sure if this is the best approach...
any thoughts/ideas/comments from people who are really familiar with
subversion? has anyone else run into this kind of need...
the issue basically boils down to how you can use subversion in a system
where the users and files are dynamically changing...
thanks
-bruce
bedouglas@earthlink.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 19 17:06:53 2006