On 9/28/2010 2:23 PM, Tech Geek wrote:
Do not put your repository on a shared drive. Do not use file: protocol to access it. It is not designed to work in such way. Read the documentation (aka svnbook) and configure a proper server.This should be emphasized more. Although the OP said he wanted the users to be able to create new repositories, it is really a bad idea to be able to do this through mapped file access (aside from that being a bad idea in general for multiuser use) because it also means that anyone can delete or overwrite your entire history with an inadvertent typo or mouse wiggle. Once the repository is created the users will be accessing it either through svn:// or http:// and NOT with file:/// Although I still want the users to be able to create repository using TSVN because they are not familiar with Linux at all and also that they won't have to wait for some admin person (let's say myself) to just create a repository for them.
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.
-- Les Mikesell lesmikes...@gmail.com
