[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Accessing Remote SVN Repositories

From: Geoff Hoffman <ghoffman_at_cardinalpath.com>
Date: Wed, 17 Jul 2013 16:06:32 -0700

Steve, first off, the security permissions you may need as a prerequisite
to access "their stuff" covers a wide range of scenarios: SSH keys, VPN
access and so on are outside the range of topics discussed here. Let's
assume you have access past their firewall to the server where their stuff
is stored.

As Ryan suggested, presumably they will or have already provided you with a
URI (it may start with http://, https://, svn://, or svn+ssh:// ... ) [1]
and you may have more than one set of un/pw combo.

If you never need to push changes you make to their stuff, back to their
repository, just ask them for an svn export (zip) one-time, as it will be
simpler for a beginner.

If however, you are going to be expected to deal with changes they make to
their stuff on an ongoing basis (svn update your local copy ~ analogous to
git pull), and the standard way you can deal with "your stuff" going to
"your repository" while changes to "their stuff" can be integrated with
"your stuff" -- all at the same time -- is via the concept of

In these cases, you probably will need to integrate their stuff into your
stuff as an "external" - see here [2].

It should also be mentioned that it may be simple for them to simply host
your stuff too on the same server - as it sounds like they're already set
up to do so.

[1] http://stackoverflow.com/questions/2140954/which-protocol-svn-or-https

Geoff Hoffman
Solutions Architect & LAMP Engineer
phone +1 623.399.4918
mobile +1 480.231.8323
web CardinalPath.com <http://goo.gl/TuuiO>

On Wed, Jul 17, 2013 at 3:52 PM, Ryan Schmidt <
subversion-2012c_at_ryandesign.com> wrote:

> On Jul 17, 2013, at 17:34, Stephen Gorin wrote:
> > I need to access the Subversion repositories of two software vendors.
> Because of firewall issues they cannot "push" their changes to us, rather
> we have to access their repositories and "pull" the latest code from their
> sites.
> "push" and "pull" are not words used in Subversion parlance.
> Subversion repositories are available via URLs. The administrator of the
> repository will need to tell you what the URL is, and will need to open up
> access through their firewall for it. Then you access that URL with your
> svn client.

Connect with us on twitter <http://twitter.com/cardinalpath>, google+<https://plus.google.com/108076800625872227241/posts>
, facebook <http://www.facebook.com/CardinalPath>, or linkedin<http://www.linkedin.com/company/cardinal-path>
Catch our next training in San Francisco Jul 15 - 19<http://training.cardinalpath.com/google-adwords-analytics/san-francisco/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=sanfrancisco-2013-07-15#2013-07-15>
, Philadelphia Jul 22 - 26<http://training.cardinalpath.com/google-adwords-analytics/philadelphia/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=philadelphia-2013-07-22>
, Detroit Jul 29 - Aug 2<http://training.cardinalpath.com/google-adwords-analytics/detroit/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=detroit-2013-07-29>
, Columbus, Aug 5 - 9<http://training.cardinalpath.com/google-adwords-analytics/columbus/?utm_campaign=cp-cpt&utm_source=sig-referral&utm_medium=email&utm_content=columbus-2013-08-05>
 or See All<http://training.cardinalpath.com/locations/?utm_campaign=cp-s4s&utm_source=cp-email-footer&utm_medium=email&utm_content=see-all>
This email, including any attachments, is for the sole use of the intended 
recipient and may contain confidential information. If you are not the 
intended recipient, please immediately notify us by reply email or by 
telephone, delete this email and destroy any copies. Thank you.
Received on 2013-07-18 01:07:04 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.