RE: Create Repository Remotely

Generally we use one repository and allow people to create new folders
in it. Why do you need a new repository for each "thing"?

BOb

________________________________

From: Aaron Searle [mailto:searle.aaron_at_gmail.com]
Sent: Friday, March 20, 2009 12:11 AM
To: users_at_subversion.tigris.org
Subject: Create Repository Remotely

I have several repositories that I maintain on a single server, and I am
working towards a svnsync to a disaster recovery (DR) server soon. I am
planning to host both src and sink on linux boxes. As it stands right
now I have to ssh into my main server, create a repository, copy all the
hook scripts to the right place. Then ssh into the DR server, and do
the same steps, including a different set of hook scripts Then go back
to the main server and initialize the svnsync.

What I cannot figure out is how people commonly add / maintain
repositories in such a way that they can make / call a single command
that will:

1. Create the new repository.
2. Remotely create the svnsync repository.
3. Copy over all pre and post commit scripts.
4. Initialize the svnsync

Without having to go through these steps each time.

So can I,

1. Remotely create repositories on my DR server?
2. Put my hook scripts into a template of some fashion, so every time I
make a new repository my hook scripts are automatically put into the
/hooks directory?
3. Be able to create one script to do all the work for me?

What are the common ways of administering this? I am sure others have
the same problem as me.

a

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1366043

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-20 18:30:11 CET