You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Aaron Searle <se...@gmail.com> on 2009/03/20 04:10:53 UTC
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=1361095
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Create Repository Remotely
Posted by Aaron Searle <se...@gmail.com>.
We have repository per company / acquisition that we own. As well as major
project go into their own repository.
a
On Fri, Mar 20, 2009 at 11:28 AM, Bob Archer <Bo...@amsi.com> wrote:
> 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@gmail.com]
> *Sent:* Friday, March 20, 2009 12:11 AM
> *To:* users@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=1366439
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: Create Repository Remotely
Posted by Bob Archer <bo...@amsi.com>.
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@gmail.com]
Sent: Friday, March 20, 2009 12:11 AM
To: users@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@subversion.tigris.org].