right...
for my thoughts, we're going to need the ability to allow users to create
svn repos based on the projects that they create. we might restrict repos
deletions to admins, etc.. so, for our needs we're going to need to create
svnadmin/svn commands that incorporate 'user' information... yeah, i know,
security issues!!!
-----Original Message-----
From: Michael Hogsett [mailto:hogsett@csl.sri.com]
Sent: Friday, April 01, 2005 1:26 PM
To: bedouglas@earthlink.net
Cc: users@subversion.tigris.org
Subject: Re: intergration of svn via php
bruce wrote:
> michael,
>
> if you do a svnadmin/svn command but don't accept user input, then i
assume
> you don't allow for the creation of user defined svn repositories...
>
> arrgghh!!
>
> bruce
>
>
That is correct. I am building a svn backed website / content management
system.
The repository contains the entire web site. Users will go to a specific
Apache virtual host to edit web pages in the web server directory tree and
then
save those changes to the working copy on the edit server. Later they will
publish those changes (commit to the repo).
The display web server periodically performs a 'svn update' of its working
copy,
thus publishing the committed changed.
- Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 2 00:06:57 2005