You should put everything on your main server. Read the chapter on
tagging and branching so people dont have to check out your "code
twitches".
There is no way to commit to two different servers. You _can_ have
one mirror another, but it would be read only, and it would be a
complete copy anyway, so your best approach would be to use branching
and tagging.
On 7/28/07, Phlip <phlip2005@gmail.com> wrote:
> Subversives:
>
> Firstly, in the documentation, does "repository" mean one group of projects
> on a server? Or does it mean one project, in that group, on the server?
>
> Knowing that helps me know if I should read documents that discuss
> "repositories".
>
> Here's the main question.
>
> I have an SVN project on server A, and I just got the keys to another
> server, B.
>
> From scratch, how to I create an _intermittent_ (not continuous) mirror on
> server B?
>
> I want to practice Continuous Integration to server A, and each time I feel
> a version tick coming on, I simultaneously 'svn ci' (or equivalent) to both
> servers.
>
> This allows users to download from server B, safe from my code twitches,
> which constantly appear on server A.
>
> Where to start? svnadmin dump? svnsync?
>
> --
> Phlip
> http://www.oreilly.com/catalog/9780596510657/
> "Test Driven Ajax (on Rails)"
> assert_xpath, assert_javascript, & assert_ajax
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 29 03:19:28 2007