You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by bruce <be...@earthlink.net> on 2006/06/19 13:25:02 UTC

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

Re: User File Access from Mysql DB... (correction)

Posted by Joerg Hessdoerfer <Jo...@sea-gmbh.com>.
Hi,

On Monday 19 June 2006 19:30, bruce wrote:
> hi joerg...
>
> do you write to the ACL db/file everytime a user changes their access
> requirements regarding a given file... do you also write to the ACL db/file
> everytime a file moves from folder to folder...
>
> for my app, the file moves between processes, and since a user might have
> access to one process and not another.. i need to solve this.
>
> the only way i can see is to add/delete the users within the ACL file as
> the "file" moves along the process, which is going to require a lot of
> update hits to the ACL by my app..
>
> another approach would be to simply rewrite a new ACL file from a db on
> every file/process change...
>
> -bruce
[...]

yep, that's what we do - re-write it on every databse change. But we only do 
have user's access rights changes, and we don't track individual file 
locations, as they usually don't move.

Re-writing the ACL is really fast in our case - and can probably be done from 
a cron job every couple of minutes. Just create some trigger file when the DB 
changes, an re-generate from cron if the file exits.

Greetings,
	Jörg
-- 
Leiter Softwareentwicklung - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: User File Access from Mysql DB... (correction)

Posted by bruce <be...@earthlink.net>.
hi joerg...

do you write to the ACL db/file everytime a user changes their access
requirements regarding a given file... do you also write to the ACL db/file
everytime a file moves from folder to folder...

for my app, the file moves between processes, and since a user might have
access to one process and not another.. i need to solve this.

the only way i can see is to add/delete the users within the ACL file as the
"file" moves along the process, which is going to require a lot of update
hits to the ACL by my app..

another approach would be to simply rewrite a new ACL file from a db on
every file/process change...

-bruce


-----Original Message-----
From: Joerg Hessdoerfer [mailto:Joerg.Hessdoerfer@sea-gmbh.com]
Sent: Monday, June 19, 2006 10:17 AM
To: users@subversion.tigris.org; bedouglas@earthlink.net
Subject: Re: User File Access from Mysql DB... (correction)


Memory didn't serve -
> (or newer svnserve, 1.3.X if memory serves?)

it's 1.4, which is not yet released. I use apache ;-)

Greetings,
	Jörg
--
Leiter Softwareentwicklung - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com

---------------------------------------------------------------------
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

Re: User File Access from Mysql DB... (correction)

Posted by Joerg Hessdoerfer <Jo...@sea-gmbh.com>.
Memory didn't serve - 
> (or newer svnserve, 1.3.X if memory serves?)

it's 1.4, which is not yet released. I use apache ;-)

Greetings,
	Jörg
-- 
Leiter Softwareentwicklung - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: User File Access from Mysql DB...

Posted by ja...@subversus.org.
The question also arises as to whether or not you want a process editing
your access files, especially if this is something that happens at a
frequent basis.  This almost sounds like a recipe for disaster especially in
the form of corruption of your user / access rights files.  At least if you
keep the information in the database the DB server can generally
self-recover in the event of unexpected system events.


-----Original Message-----
From: bruce [mailto:bedouglas@earthlink.net] 
Sent: Tuesday, June 20, 2006 7:05 AM
To: 'Nico Kadel-Garcia'; 'Joerg Hessdoerfer'; users@subversion.tigris.org
Subject: RE: User File Access from Mysql DB...

hi nico...

your solution essentially needs to rewrite the svn user/file access rights
file each time a user's ability/need to access a file changes.. this could
get to be a pretty big hit depending on how the workflow process is setup,
how many times a file changes as it moves between the workflow phases, as
well as the number of times a given user's access rights change...

which is why i was interested in knowing if anyone had managed to hook up a
db for both the SVN server access rights, as well as the SVN Client
access...


thanks

-bruce


-----Original Message-----
From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
Sent: Monday, June 19, 2006 7:40 PM
To: Joerg Hessdoerfer; users@subversion.tigris.org;
bedouglas@earthlink.net
Subject: Re: User File Access from Mysql DB...



----- Original Message -----
From: "Joerg Hessdoerfer" <Jo...@sea-gmbh.com>
To: <us...@subversion.tigris.org>; <be...@earthlink.net>
Sent: Monday, June 19, 2006 1:13 PM
Subject: Re: User File Access from Mysql DB...


> Hi,
>
> On Monday 19 June 2006 15:25, bruce wrote:
>> 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...
>>
> [...]
>
> well, the first thought that came to mind is a small database holding the
> user/file access rights, and a small (web-based?) app to manage those. If
> SVN
> is served by apache  (or newer svnserve, 1.3.X if memory serves?), you can
> then create per-URL access files to be directly used by SVN (see
>
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serve
rconfig.httpd.authz.perdir).
> I use a scenario like this with apache, and it works fine. I also use
> PostgreSQL as database, and write the ACL file with python using a
> post-update/insert/delete database trigger.
>
> Then there is no need to interface the auth mechanism to anything else.

Too complex. Take a good close look at svnaccess.pl and the matching
svnconfig file in the contribs directory of the Subversion source tree. By
simply setting appropriate privileges for specific users for directories
with specific names, you can restrict their read, create, delete, and modify
permissions separately. This allows you to create "tags" that are stable
until the site administrator moves or deletes them, or to restrict write
access in other clever ways. And correctly implemented, the permissions will
apply both to local users, svnserve users, and HTTP users.

---------------------------------------------------------------------
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

RE: User File Access from Mysql DB...

Posted by bruce <be...@earthlink.net>.
hi nico...

your solution essentially needs to rewrite the svn user/file access rights
file each time a user's ability/need to access a file changes.. this could
get to be a pretty big hit depending on how the workflow process is setup,
how many times a file changes as it moves between the workflow phases, as
well as the number of times a given user's access rights change...

which is why i was interested in knowing if anyone had managed to hook up a
db for both the SVN server access rights, as well as the SVN Client
access...


thanks

-bruce


-----Original Message-----
From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
Sent: Monday, June 19, 2006 7:40 PM
To: Joerg Hessdoerfer; users@subversion.tigris.org;
bedouglas@earthlink.net
Subject: Re: User File Access from Mysql DB...



----- Original Message -----
From: "Joerg Hessdoerfer" <Jo...@sea-gmbh.com>
To: <us...@subversion.tigris.org>; <be...@earthlink.net>
Sent: Monday, June 19, 2006 1:13 PM
Subject: Re: User File Access from Mysql DB...


> Hi,
>
> On Monday 19 June 2006 15:25, bruce wrote:
>> 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...
>>
> [...]
>
> well, the first thought that came to mind is a small database holding the
> user/file access rights, and a small (web-based?) app to manage those. If
> SVN
> is served by apache  (or newer svnserve, 1.3.X if memory serves?), you can
> then create per-URL access files to be directly used by SVN (see
>
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serve
rconfig.httpd.authz.perdir).
> I use a scenario like this with apache, and it works fine. I also use
> PostgreSQL as database, and write the ACL file with python using a
> post-update/insert/delete database trigger.
>
> Then there is no need to interface the auth mechanism to anything else.

Too complex. Take a good close look at svnaccess.pl and the matching
svnconfig file in the contribs directory of the Subversion source tree. By
simply setting appropriate privileges for specific users for directories
with specific names, you can restrict their read, create, delete, and modify
permissions separately. This allows you to create "tags" that are stable
until the site administrator moves or deletes them, or to restrict write
access in other clever ways. And correctly implemented, the permissions will
apply both to local users, svnserve users, and HTTP users.

---------------------------------------------------------------------
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

Re: User File Access from Mysql DB...

Posted by Nico Kadel-Garcia <nk...@comcast.net>.
----- Original Message ----- 
From: "Joerg Hessdoerfer" <Jo...@sea-gmbh.com>
To: <us...@subversion.tigris.org>; <be...@earthlink.net>
Sent: Monday, June 19, 2006 1:13 PM
Subject: Re: User File Access from Mysql DB...


> Hi,
>
> On Monday 19 June 2006 15:25, bruce wrote:
>> 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...
>>
> [...]
>
> well, the first thought that came to mind is a small database holding the
> user/file access rights, and a small (web-based?) app to manage those. If 
> SVN
> is served by apache  (or newer svnserve, 1.3.X if memory serves?), you can
> then create per-URL access files to be directly used by SVN (see
> http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir).
> I use a scenario like this with apache, and it works fine. I also use
> PostgreSQL as database, and write the ACL file with python using a
> post-update/insert/delete database trigger.
>
> Then there is no need to interface the auth mechanism to anything else.

Too complex. Take a good close look at svnaccess.pl and the matching 
svnconfig file in the contribs directory of the Subversion source tree. By 
simply setting appropriate privileges for specific users for directories 
with specific names, you can restrict their read, create, delete, and modify 
permissions separately. This allows you to create "tags" that are stable 
until the site administrator moves or deletes them, or to restrict write 
access in other clever ways. And correctly implemented, the permissions will 
apply both to local users, svnserve users, and HTTP users. 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: User File Access from Mysql DB...

Posted by Joerg Hessdoerfer <Jo...@sea-gmbh.com>.
Hi,

On Monday 19 June 2006 15:25, bruce wrote:
> 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...
>
[...]

well, the first thought that came to mind is a small database holding the 
user/file access rights, and a small (web-based?) app to manage those. If SVN 
is served by apache  (or newer svnserve, 1.3.X if memory serves?), you can 
then create per-URL access files to be directly used by SVN (see 
http://svnbook.red-bean.com/nightly/en/svn.serverconfig.httpd.html#svn.serverconfig.httpd.authz.perdir). 
I use a scenario like this with apache, and it works fine. I also use 
PostgreSQL as database, and write the ACL file with python using a 
post-update/insert/delete database trigger.

Then there is no need to interface the auth mechanism to anything else.

HTH,
	Jörg
-- 
Leiter Softwareentwicklung - S.E.A GmbH
Mail: joerg.hessdoerfer@sea-gmbh.com
WWW:  http://www.sea-gmbh.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: User File Access from Mysql DB...

Posted by ja...@subversus.org.
You are correct... in our application all access will run through a web
application.  In which case, things come together quite nicely. However, if
you want to allow individuals access through svn client apps, things fall
apart quite quickly.  The only downside that I see to running everything
through a web app (and has been asked to me) is dealing with the situation
where you need to handle a large number of files (such as a project with
many files, all of which need to be uploaded together and approved as a
whole).  To which my response was... "don't do that".  :-)

I *suppose* you could handle both web app and svn client app access through
a series of action hooks, but I haven't used Subversion hooks much and don't
know the extent to which they allow control.  Plus, I don't really think
they were intended for such fine-grained control.  And I still don't know
how a person would "request" access to a particular file / folder, even with
hooks implemented.

I have started development on the document workflow app.  I'm about a week
or two away from a functional system.  Or at least something that doesn't
break on every other page served.  I don't see why I couldn't release it
openly... I'm just not sure how many people who'd want such a system though.
:-)


-----Original Message-----
From: bruce [mailto:bedouglas@earthlink.net] 
Sent: Monday, June 19, 2006 11:08 AM
To: jason@subversus.org; users@subversion.tigris.org
Subject: RE: User File Access from Mysql DB...

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

RE: User File Access from Mysql DB...

Posted by bruce <be...@earthlink.net>.
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

RE: User File Access from Mysql DB...

Posted by ja...@subversus.org.
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

RE: User File Access from Mysql DB...

Posted by bruce <be...@earthlink.net>.
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

RE: User File Access from Mysql DB...

Posted by ja...@subversus.org.
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