On 9/28/2010 6:20 PM, Tech Geek wrote:
> Les,
>
> The point remains that if they have write access through mapped
> files, they have the capability of destroying everything there.
>
> You could probably whip up a cgi script to create new
> repositories from a web request form if something like that
> doesn't already exist. Or you could put more than one project
> inside a single repository so all you have to do is create a new
> top level directory with the trunk/branches/tags structure under
> it. There are some downsides, but it is not an unreasonable
> approach and it lets users do everything remotely.
>
> I do undestand your concern but in our case we don't have any option
> other than putting repositories on the network drives. Let's just say
> our hands are tied.
I thought you said they were accessing it via svn or http protocols
after creation.
> Having just a top level repository is also not viable in our case. We
> need one repository per project.
> My only other option now is to try upgrading the SVN server on the Linux
> machine...
Your other option is to give the users a more reasonable way to create
the repos. If you trust them not to destroy everything with their
mapped file connection you should be able to trust them to log into the
linux server with putty (etc.) and type the svnadmin create command with
a sudo configuration or simple group write access to the target
directory. Or, as I mentioned before, a web form posting to a cgi
script that does the creation (and maybe some sanity checks) is really
all you need, and then you don't have to worry about keeping the server
and all clients strictly in sync.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2010-09-29 19:14:15 CEST