On 5/3/06, John Biddiscombe <email@example.com> wrote:
> I have asked our sysadmins to setup a server for svn which they have
> done using an apache interface. I have a repository working with a
> project inside it.
> I now need to create about half a dozen new projects, each with
> different user access rights, some public, some open to certain users,
> some a combination of either.
> I have asked the sysdmins to setup things, but they are not experienced
> svn users and neither am I, also they just don't have time to help me
> out. I can't wait for them and would like to set things up myself, but I
> have no "privileges" and can't change users, repository locations etc in
> the apache configurations.
> Is there some way that the admins can allow me to create
> projects/repositories/users and change access rights etc without me
> being a root user and without allowing me to break the entire system (I
> am not an admin and am quite likely to break stuff initially until I
> have learned the ropes).
> Is there FAQ of some kind that can help me. I've read the svn book, but
> need more help.
This really isn't an SVN question so much as a general system admin
(for whichever OS you're using) question.
For the SVN config file, they should be able to assign you to a group,
and then give that group write permission on the file. This is pretty
trivial. For the Apache config (which really, you shouldn't need to
modify much once it's set up), they can do the same, but they'd also
need to grant you rights to restart apache. On UNIX/Linux, sudo is
made for just this sort of situation. Note that you do not need to
restart Apache when editing your subversion config file - changes take
I'd also recommend that you create your own SVN environment that
mimics your "live" one, at least as far as configuration goes, on your
own workstation. That way you can test configurations out and then
send the admins the changes to apply to the real server (assuming they
can't do the above) and get it "right" the first time where it counts.
The server admin won't need to know SVN at all, they just have to
apply the changes you give them to the files you specify. This is how
I'm set up.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 3 15:37:53 2006