Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Is your "supplier" a serious company? I can think of next to no reason a serious software company would not have broadband Internet access and if they have they almost with certainty have a firewall in place at the point of entry to the internal LAN. The only thing needed to gain access to the CVSNT server that sits on this LAN is to create a port forwarding rule for TCP port 2401 on the firewall to point to the CVSNT server. And then you should disable :pserver: and instead use :sserver: for access (sserver is encrypted). Now you will have full access via the Internet to the server from both locations. This talk about diffs being slow is not something I have experienced myself, usually diffing for example Tony's CVSNT code to find out what has been done is a matter of a couple of seconds over the Internet. Best regards, Bo Berglund -----Original Message----- From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Bernhard Merkle Sent: den 29 november 2005 09:36 To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] mirror/synchronize cvs repositories (CVSNTUpd) ? > I don't really understand why you and your supplier cannot share the > same CVS server. I think that you are imaging the shortcomings of > other version control tools onto CVS and then you think you have to > solve a problem that is not even there! The problem with performance is not so much ci/co but more diff etc. The line to the provider is very thin, and also oneway. (we can not dial in at the provider, but they can dial at us). So because of performace reasons, the repo should be at the provider. But we also want to access the repo, but can not dial in there. So what to do ? I can only think of: repo a the provider and mirror this to us, so that we have a read-only copy of the repository. The problem then comes when WE want to do checkins, because the repo is not write accessible. (because of the dial restriction). So I have to solve a problem that is really there ! ;-) any idea ? kind regards, Bernhard. _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs