Hi guys,
Anyone have suggestions on replicating svn repo's?
I tried this script
https://open.datacore.ch/read-only/svnreplicate/trunk/README with little
success other then with file:// protocol.
I need to keep two repo's in sync.
Repo1 and repo2
Repo1 needs to be able to be updated even if repo2 is down but repo2 can
be made to wait for commits until repo1 is available.
We need to be able to commit on either repo and have the data updated on
both repo's but one could have
So I am trying to run a two way replication with a master/slave setup.
Any suggestions would be appreciated.
Regards,
Rey
--------------------------------------------------------------------------------------------------------
This message and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom it is
addressed. It may contain sensitive and private proprietary or legally
privileged information. No confidentiality or privilege is waived or
lost by any mistransmission. If you are not the intended recipient,
please immediately delete it and all copies of it from your system,
destroy any hard copies of it and notify the sender. You must not,
directly or indirectly, use, disclose, distribute, print, or copy any
part of this message if you are not the intended recipient.
FXDirectDealer, LLC reserves the right to monitor all e-mail
communications through its networks. Any views expressed in this
message are those of the individual sender, except where the
message states otherwise and the sender is authorized to state them.
Unless otherwise stated, any pricing information given in this message
is indicative only, is subject to change and does not constitute an
offer to deal at any price quoted. Any reference to the terms of
executed transactions should be treated as preliminary only and subject
to our formal confirmation. FXDirectDealer, LLC is not responsible for any
recommendation, solicitation, offer or agreement or any information
about any transaction, customer account or account activity contained in
this communication.
Received on Wed Jun 6 01:02:25 2007