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

Re: Connecting TSVN to server

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Mon, 15 Jun 2009 21:44:10 +0100

2009/6/15 manogolf <manogolf_at_charter.net>:
> I am seeking the dumbed down version of connecting TSVN to my server. Reading
> network settings section provides instruction for proxy, (not going through
> a company firewall)

Do you actually have a proxy?

> and access to a svn+ssh repository (I just want to
> checkout a file from my server to my local machines repository and then
> commit back with version control). Using import from the local repository
> folder and entering URL of the folder I want from the server returns:
> OPTIONS of 'http://myipaddress/home/drupal6/sites': 200 OK
> (http://myipaddress)

Why are you using http:// to access an svn server? You would need to
specify svn+ssh://

> Am I required to create a repository on my server as well as having one on
> my local machine? I figured one use of TSVN was to act as a local machine
> repository (if that was all you required; I don't need to share a repository
> from my server at this time, or am I  entirely missing how TSVN is used?)
> for checking out from a server and initiating version control of folders and
> files then pushing them back to the server.

First of all you need to understand the difference between a
repository and a working copy. Subversion is a centralised version
control system so there is exactly 1 master repository to which
changes are committed, and which holds all the history. On your local
PC you checkout a working copy which is your personal sandbox for
working in.

You can also get distributed VCS where every PC has its own copy of
the repository with full history, but Subversion ain't one of them.

Next, using svn+ssh is not for the faint hearted and it is certainly
not the easy option.

If you work alone on only one PC you can use file:// access to a
repository on your own PC.

If you need to access from several different PCs and/or you need more
than one person to access the data then you need to set up a server.
Plain svn:// is extremely simple to set up if you are not worried
about encryption of the data as it travels over the wire. You can add
encryption using SASL which is also described here:

If you want to use http:// access the easiest method is to get the
free VisualSVN server which will (I believe) install the Apache server
for you. Never set up Apache myself.

If you really want to use svn+ssh there is a howto here:

Please take the time to read the documentation. It does describe most
of what you are asking already.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-15 22:44:21 CEST

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

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